You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to be able to have multiple repositories opened in parallel (akin to the "workspaces" in vscode and intelliJ).
For example in my case I have multiple git repositories for different parts of our as-code deployment configurations (depending on what other people require access). I regularly have changes that are similar across all repositories and create an identical structure of stacked branches in each repo (e.g. maintenance/2024-12-). It would be really cool if we could have these stacked virtual branches shown as one group despite being multiple different repos in the background.
The text was updated successfully, but these errors were encountered:
Even though I would find it unlikely that GitButler could be changed to be able to support this, an alternative to that could be the ability to recreate a certain stack, along with its patches, in another repository using a (future) CLI maybe, or by exporting a file that can be imported into other repositories with the UI even.
That way it would be possible to achieve something similar with multiple Windows open. Please do let me know if I am missing a key point which wouldn't be covered by the approach I mentioned.
Thanks again.
It would be great to be able to have multiple repositories opened in parallel (akin to the "workspaces" in vscode and intelliJ).
For example in my case I have multiple git repositories for different parts of our as-code deployment configurations (depending on what other people require access). I regularly have changes that are similar across all repositories and create an identical structure of stacked branches in each repo (e.g. maintenance/2024-12-). It would be really cool if we could have these stacked virtual branches shown as one group despite being multiple different repos in the background.
The text was updated successfully, but these errors were encountered: