git worktree
(this is #bonuscomic #3 for "How Git Works" https://wizardzines.com/zines/git, covering some topics that I didn't talk about in the zine)
Also I don't use worktrees very rarely, so please reply with gotchas/tips about worktrees if you use them more!
Follow
@b0rk tip: iff you frequently have to pause/resume work on a project foo (due to waiting for feedback from reviewers or god forbid waiting for CI), I suggest keeping two worktrees named foo and foo2. It removes the need for rebuilding the project when switching branches as well as avoiding tricky git stash/pop.
@b0rk it's for situations that can be described as "it's currently a mess of new test files, logs, and hacks that maybe shouldn't be committed or at least need some cleanup before it makes sense to add them to git"