Add multi-repository tree view#139
Open
rjerue wants to merge 4 commits into
Open
Conversation
letmaik
reviewed
May 3, 2026
Owner
letmaik
left a comment
There was a problem hiding this comment.
Pretty cool!
I gave it a try and noticed two issues:
- "Search changes" seems broken, the include filter is empty
- The Refresh button seems to operate on the repo currently selected in the tree, which is a little confusing, should probably refresh all
Author
|
Will take a look at comments this weekend. Thanks for taking a look |
Author
|
Ok, did not use the search functionality on the prior testing. Looks to be working now. Refresh is now also broken up into refreshAll and refresh. Thanks for considering! |
|
I agree with @rjerue. I also have multiple repos in my workspace and would like to view the diffs simultaneously. This PR seems to add the exact functionality I was looking for! thank you both for you work! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
I love this extension and use it more than VS Code's built-in Git view for reviewing changes. One thing I kept wanting for my workflow was the ability to see changes across multiple repositories in the same workspace without switching the active repository manually. I often have several repos with 1-2 files changed in them.
This PR adds an experimental
gitTreeCompare.multiRepositoryViewsetting. When enabled, Git Tree Compare shows one expandable section per open Git repository. The default behavior is unchanged.Screenshot
What Changed
gitTreeCompare.multiRepositoryViewfeature flag to settings.Why
I work in multi-root workspaces where related changes often span several repos. The current extension can compare one repository at a time, but switching back and forth makes review prep harder than it needs to be.
This keeps the existing single-repo flow intact while making the multi-repo workflow available behind a flag.
My intent is to use my own fork regardless. I am also going to have a private build that integrates with some internal tooling from my company, but I wanted to offer the agnostic parts back here in case they are useful to others and would happily make that an upstream.
I kept this scoped to the generic multi-repository behavior.
That said,
treeProvider.tsis doing a lot already, and this change adds more state management to it. It may be that this should land differently, or thattreeProvidershould be refactored first before taking on multi-repository state. If there are gotchas in the extension architecture, UX concerns, or a preferred direction for how to structure this, I am happy to adjust.Manual Testing