Can't distinguish different worktrees of single repo
See original GitHub issueFor some of the projects I’m working on I have multiple git-worktree
s set up, but these all show up as the same project name, which makes it quite annoying to work with.
How I think this could be solved is by displaying the branch that is currently checked out for the worktree.
Btw, this is not the same as; https://github.com/desktop/desktop/issues/907
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:5 (4 by maintainers)
Top Results From Across the Web
git - difference between worktrees and shared repositories?
A clone that uses --shared (or the implied --shared from some pathname-based clones) is a separate repository. By using hard links 1 (which ......
Read more >git-worktree Documentation - Git
A git repository can support multiple working trees, allowing you to check out more than one branch at a time. With git worktree...
Read more >Branch Management With Git Worktree - Dev Notes
If you need to frequently switch between Git branches, the worktree feature can be a useful way of working since it allows you...
Read more >Ubuntu Manpage: git-worktree - Manage multiple working trees
A git repository can support multiple working trees, allowing you to check out more than one branch at a time. With git worktree...
Read more >Parallelize Development Using Git Worktrees - Atomic Spin
Gits worktrees give you an extra working copy of your repository, ... have to push one repo to the remote and then pull...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @koenpunt thanks so much for filing this. I think the proposed solution here makes sense as an incremental step but I would love to get some input from design before we jump into implementation.
While this was “merged” into #6460, that one was closed, but I think this is still an issue. The main difference between this and #6460, is that subtrees are a git feature, and the other proposals are about organizing repos outside of git functionality.
The support for worktrees in general is subpar; I just opened another issue regarding them.
And also trying to checkout a branch that’s already checked out in a different worktree renders an error, instead of something more helpful.
So I would really appreciate it if my proposal could be reevaluated.