Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Tree View for Changed Files in the Workspace Panel #7036

Open
jeffercbs opened this issue Feb 9, 2025 · 1 comment
Open

Comments

@jeffercbs
Copy link

Description

Currently, the workspace panel in GitButler lists changed files in a flat structure. While this is useful for quick access, it becomes less effective when working with larger projects that have deeply nested directories. A tree view representation of the file changes, similar to how IDEs like VS Code display files in a structured hierarchy, would improve usability and navigation.

Expected Behavior

The workspace panel should provide an optional tree view mode for displaying changed files. Folders should be collapsible/expandable to allow for better organization. The structure should mirror the repository's directory hierarchy. Visual indicators (e.g., icons, colors) should highlight modified, new, and deleted files within their respective directories. Option to toggle between flat list and tree view for user preference.

Use Case

Developers working on large projects with multiple nested folders often struggle to find specific changed files quickly. A tree view helps maintain context by showing how files relate to their parent directories. Enhancing visibility can improve the workflow when staging specific files or reviewing changes. Additional Context I've attached an example screenshot (from VS Code) that illustrates the desired behavior:

Image

Would love to hear if this is already on the roadmap or if I can contribute to implementing this feature! 🚀

@Megasware128
Copy link

Duplicate of #5482

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@Megasware128 @jeffercbs and others