Jujutsu worktrees are convenient (2024)

(shaddy.dev)

128 points nvader | 2 comments | 03 Dec 25 23:26 UTC | HN request time: 0s | source

Show context

Zambyte ◴[08 Dec 25 10:15 UTC] No.46190590[source]▶

I'm glad they found a workflow that works for them, but

> but for some reason I cannot proceed on it while eg the CI is running, but I also don’t want to leave the commit and close my code editor etc. It would be simple to just stash everything and later pop the stash, but it still feels disruptive.

I have been using jj as my git client for 2 years now (wow), and I have never considered this to be disruptive. I just immediately switch to a new commit where I want to go, rather than making a new workspace to work in. Maybe it's a difference in the editor that I use (GNU Emacs) that makes this more natural?

replies(2): >>46190618 #>>46190910 #

1. rafaelmn ◴[08 Dec 25 10:19 UTC] No.46190618[source]▶

>>46190590 #

Build cache, packages and a few of other things get messed up when switching branches - if you need to do a "quick bug-fix and get back into the main thing" worktrees are really nice.

replies(1): >>46191889 #

2. Zambyte ◴[08 Dec 25 13:20 UTC] No.46191889[source]▶

>>46190618 (TP) #

I see. The projects I have been working on in the last few years don't take very long to compile, so build cache has not been a very big factor for me. I could see it being more important for projects that take a long time to build though.

↑