Sync GitHub Issues with GitButler Virtual Branches

[noamsiegel]

I'd like to propose and contribute to a feature that would sync GitHub repository issues with GitButler virtual branches. This integration could significantly improve workflow efficiency for developers using both platforms.

I can work on this myself, but I need these questions answered first:

• Is this feature aligned with GitButler's roadmap?
• What would be the best approach to implement this integration?
• Are there any existing efforts or discussions around this topic?

I'd like to have a veteran walk me through (either on a call or a recording) these questions so that I can contribute as soon as possible. Or, a well-detailed explanation in the comments below would suffice!

[Byron]

Hi @noamsiegel , thanks for asking!

Without my answer being authoritative at all, I'd think anything that improves the efficiency of its users is aligned with GitButler - it's here to serve :).

Before discussing specifics, I think it would be great to learn from you how you would use such a feature, in enough detail to understand how it would work. For instance, taking the proposition literally my GitButler would now have 243 lanes, one for each issue, which probably isn't what you had in mind - I am clearly missing something. Everything you can write to help others align with your initial vision would be greatly appreciated.

Let me also CC @krlvi who is always interested in improved workflows as well.

[Byron]

Thanks for elaborating! This sounds quite straightforward to me, so straightforward in fact that I'd think somebody like @PavelLaptev might have thought about it already.

In any case, this is probably it from me for the first gathering and clarification of the issue at hand, let's see when others chime in to figure out if it makes sense to tackle this.

[noamsiegel]

No problem! I'll wait for other opinions/responses in the meantime.

[noamsiegel]

Any update on this @Byron?

[PavelLaptev]

@noamsiegel Thanks for the idea! Right now, we're working on the design for V3, where the "branches" sidebar will move to a separate page, so the classic sidebar will go away.

There could be a separate page for "issues" too, but that's not a priority at the moment. My suggestion is to keep this idea for later, once we have a better understanding of V3. Prototypes or concepts are always welcome, though they wouldn’t be implemented yet as the app is currently in a transition phase. @krlvi, feel free to correct me.

[noamsiegel]

@PavelLaptev This sounds great; I'll keep this on the back burner until V3 is released. Thanks for the update!