Very cool. I've been using worktrees a lot recently at work, mostly reworking tools or CI jobs that try to manage branches into just using a worktree and cleaning up after yourself.
It's made a big difference in readability and cleanliness. I'll often use, eg, `mktemp -d` with a template argument that's relevant to the usage, then use the base name of the temporary directory as the worktree branch, followed by `git fetch <remote> <remote-branch>:<worktree-branch>`.
I've been thinking about using worktrees more for my general development, since I'm frequently working across multiple branches.
It's made a big difference in readability and cleanliness. I'll often use, eg, `mktemp -d` with a template argument that's relevant to the usage, then use the base name of the temporary directory as the worktree branch, followed by `git fetch <remote> <remote-branch>:<worktree-branch>`.
I've been thinking about using worktrees more for my general development, since I'm frequently working across multiple branches.