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.
These things are very cool. I buy wood from a local wood yard every year or two (I don't use much here in Texas, but we do love our firepit and fireplace when it's cool enough), but the splits I get are often too large to easily burn. I'll often buy a bag of kindling when I pickup fire wood, but the kindling doesn't last long.
The main reason I didn't get a kindling cracker is because I don't have a stable base to mount it, although I suppose I could manufacture one next to the wood rack. I did, however, get a hydraulic wood splitter[1] which at least helps split some of the really large logs into something more manageable. It's pretty simple to use and very effective, even on the very knotty and hard oak wood out here.
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.