←back to thread

128 points nvader | 1 comments | | HN request time: 0.195s | source
Show context
amluto ◴[] 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 #
Normal_gaussian ◴[] No.46191388[source]
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 #
gcr ◴[] No.46191800[source]
What if the sandbox needs access to the history? Imagine asking for help bisecting something, for example
replies(4): >>46192694 #>>46192764 #>>46198421 #>>46199117 #
1. ◴[] No.46192694[source]