Jujutsu worktrees are convenient (2024)

(shaddy.dev)

Show context

amluto ◴[08 Dec 25 11:40 UTC] No.46191145[source]▶

I want a variant of this where I make a worktree that has no ability to push anywhere including its parent. Instead the parent worktree pulls from it automatically. That way I can run some sandboxed workflow that might arbitrarily corrupt the work tree, possibly overwriting everything in it and symlinked from it, without losing data.

replies(2): >>46191388 #>>46191787 #

1. Normal_gaussian ◴[08 Dec 25 12:17 UTC] No.46191388[source]▶

>>46191145 #

The easy way to do this is to create a worktree and then just run it in some form of sandbox - e.g. a Docker container.

In the worktree there is no .git directory, just a .git file which has a single line: "gitdir: <path to gitdir>".

If your sandbox doesn't have access to the gitdir, you're golden.

replies(1): >>46191800 #

2. gcr ◴[08 Dec 25 13:12 UTC] No.46191800[source]▶

>>46191388 (TP) #

What if the sandbox needs access to the history? Imagine asking for help bisecting something, for example

replies(4): >>46192694 #>>46192764 #>>46198421 #>>46199117 #

3. ◴[08 Dec 25 14:37 UTC] No.46192694[source]▶

>>46191800 #

4. Normal_gaussian ◴[08 Dec 25 14:43 UTC] No.46192764[source]▶

>>46191800 #

Then you'll probably want a clone; which will cost in more space. Just remember to remove the remotes.

You could always use an overlayFS with the main (non-worktree) repo as the lowerdir (and then remove the remotes in the overlayFS), but that relies on you not trying to keep working on the git repo at the same time.

5. amluto ◴[08 Dec 25 22:20 UTC] No.46198421[source]▶

>>46191800 #

Or if I want the sandbox to be able to create commits, which is extremely useful.

6. adastra22 ◴[08 Dec 25 23:26 UTC] No.46199117[source]▶

>>46191800 #

Mount the parent read-only.

↑