As the other guys answer this question, I put commands to delete the folder, delete worktree and delete branch here: first, list all of your worktrees to double check… $ git worktree list then, delete the folder of the worktree $ rm -rf path/to/worktree after that, delete the worktree itself $ git worktree prune in … Read more
I worked around this by erasing .git/worktrees/<branch-name> from the repository directory.
Git won’t let you check out the same branch twice, because if you do, and then go to one of the two work-trees and make a new commit, you’ll set yourself up for misery when you go back to the other work-tree. If you have actually removed the other work-tree, simply run git worktree prune … Read more
Commit a83a66a is quite clear about that: git-submodule.sh expects $GIT_DIR/config to be per-worktree, at least for the submodule.* part. Here I think we have two options: either update config.c to also read $GIT_DIR/config.worktree (which is per worktree) in addition to $GIT_DIR/config (shared) and store worktree-specific vars in the new place, or update git-submodule.sh to read/write … Read more
TL;DR: you probably wanted git worktree add ../north north First, a reminder (or information for others coming across this question): git worktree add wants to create a new work-tree and, at the same time, make sure that this new work-tree is using a different branch name from every other work-tree. This is because, while each … Read more
For me, git worktree is the biggest improvement since a long time. I’m working in enterprise software development. There, it is very common that you have to maintain old versions like what you released 3 years ago. Of course you have a branch for each version so that you can easily switch to it and … Read more