Re "stash is bad" comment, I agree, but only if you're using git in CLI. If you use something like GitKraken, then you can visually see your stashes and it's pr

Re "stash is bad" comment, I agree, but only if you're using git in CLI. If you use something like GitKraken, then you can visually see your stashes and it's pretty obvious what they're about. I find it easier to manage that way. But I definitely do the "just do a WIP commit on current branch then switch away" thing as well. I've never used worktrees, but one thing I noticed from this post is that it adds an extra FS dir layer. This would break a few workflows at my company, we use relative paths to reference sibling git repos in certain situations (e.g. to run the server in one repo which servers a build sourced from the sibling frontend repo, etc). Knowing which worktree to use in that case wouldn't really work, those scripts using relative paths would need somekind of input/arg for the worktree name.