Repository navigation
Git Panel: Show Changed Files in a Tree When Comparing Branches #66301
Closed
Dojassola
started this conversation in
Feature Requests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
What are you proposing?
When comparing the current branch against a base branch, Zed should display a navigable tree of changed files directly in the Git panel, similar to the Pull Request Changes view in VS Code.
Instead of displaying all changes in one continuous diff, Zed should list the files that were modified, added, deleted, or renamed.
Clicking a file should open its individual diff, allowing developers to review and edit that specific file while keeping the list of changed files visible.
Why does this matter?
Currently, reviewing changes between branches in Zed can be inconvenient because the changes are presented as a continuous diff rather than an organized list of files.
This becomes particularly frustrating when working with large branches containing dozens or hundreds of modified files.
This feature would make it easier to:
The goal is to provide a file-oriented branch review workflow, rather than requiring developers to navigate a single large diff.
Are there any examples or context?
VS Code — GitHub Pull Requests extension
VS Code provides a Pull Request Changes view that displays modified files in a collapsible directory tree.
Developers can select individual files to open their diffs, navigate between changes, and edit the corresponding source files.
For example:
Clicking
LoginForm.tsxopens only the changes for that file, rather than displaying the entire branch diff.This is especially useful when preparing or reviewing Pull Requests.
Possible approach
Add a Branch Changes section to the existing Git panel, activated when comparing the current branch against a base branch.
Suggested behavior:
mainordevelop.git diff base...HEAD).Ideally, this functionality should work without requiring an actual GitHub Pull Request, since comparing local branches is already a common development workflow.
The main idea is to make branch comparisons as easy to navigate as the existing Git changes panel, but for all changes introduced by the current branch relative to a selected base branch.
All reactions