There are a bunch of posts on the internet about using git worktree command. As far as I can tell,
most of them are primarily about using worktrees as a replacement of, or a supplement to git
branches. Instead of switching branches, you just change directories. This is also how I originally
had useed worktrees, but that didn't stick, and I abandoned them. But recently worktrees grew
on me, though my new use-case is unlike branching.
And cherry-pick commits done on different work trees without syncing them first. Or rebase or mergeworkk done on one work tree with others. Or check commit logs or diff them.
I use worktrees and I wondered the same question, so far here’s what I like:
git worktrees listcan show all the worktrees, you have for this same repo (not crazy value, I know)git fetchapplies to all your worktreesgit stash / applycan work across worktrees, so I can stash in one and apply it to anotherYou’re limited to a specific branch per worktree and many don’t like that but I typically from a detached HEAD anyways.
And cherry-pick commits done on different work trees without syncing them first. Or rebase or mergeworkk done on one work tree with others. Or check commit logs or diff them.