Plans to introduce worktree

[MarcosBustamante]

Are we planning to introduce git worktree concept to enable multiple agents to work in the project and not conflicting with each other? lets say that I want to work in 5 features in parallel with 5 different agents, how sapling would allow me?

[quark-zju]

You can try the "share" command for now, which creates $dst based on $src:

sl --config "extensions.share=" share --noupdate "$src" "$dst"

In .git mode, git worktree might also work.

There is a WIP worktree command, but it is currently focused on edenfs, and needs updates to work with non-eden use-cases.

[neildhar]

I have been using git worktree heavily in .git mode. I find that I have to be extremely careful because the state is not synchronized between the worktree and the original directory. For example:

1. sl pr submit doesn't really work (because sl debugvisibleheads is empty in the worktree).
2. PR metadata is not sync'd between the worktree and the original directory, which means I have to manually relink PRs in a stack after I am done working on them in a worktree. (I would love to have a mode where sapling just tracks the linked PR in the commit message, since I also sometimes need to mix git and sl operations)

I think if these were fixed, it would make it really convenient to use with worktrees.