←back to thread

Jujutsu worktrees are convenient (2024)

(shaddy.dev)
128 points nvader | 3 comments | 03 Dec 25 23:26 UTC | HN request time: 0s | source
Show context
donatj ◴[08 Dec 25 14:22 UTC] No.46192531[source]▶
I found worktrees unnecessarily painful in Git with little advantage over just having two copies of the repo.

Your far better off just having a clone of your primary repo, and have your primary repo as a local remote. Both can have a remote for GitHub and a separate remote for each other.

replies(3): >>46193828 #>>46194649 #>>46195465 #
1. loeg ◴[08 Dec 25 16:57 UTC] No.46194649[source]▶
It's very useful when your repos are a significant fraction of disk space.
replies(1): >>46203045 #
2. sph ◴[09 Dec 25 09:31 UTC] No.46203045[source]▶
Given that hard drives are in the terabytes range, which repos are you checking out in the 250+ GB ranges?

How many git users have this problem, really?

replies(1): >>46207890 #
3. loeg ◴[09 Dec 25 17:39 UTC] No.46207890[source]▶
It was the primary repo at my job at the time. Decades of history, migrated from SVN. Probably some ill-advised large binary blobs committed at one point or another.

Surely it's a tiny fraction of git repos, if not users. But if it's a problem you have, worktrees are very useful.