Run JJ Mutations Sequentially
VCS-RUN-JJ-MUTATIONS-SEQUENTIALLY
Summary
Do not overlap jj commands that write repo, working-copy, bookmark, or config state. Sequential mutations avoid locks, stale reads, and confusing operation order.
Rule
Run jj mutations sequentially.
Why
JJ mutating commands update working-copy and operation state. Running them in parallel risks locks, stale reads, and confusing operation order, especially when agents issue tool calls concurrently.
Helps
- Keeps source-control state coherent and avoids avoidable lock contention.
Limits
Read-only inspections can often run in parallel, but do not overlap commands that write jj state, working copy, bookmarks, or config.
Agent Instruction
Run jj mutations sequentially because jj mutating commands update working-copy and operation state.Mechanisms
Supported by serialized jj command execution, waiting for one mutation to finish, lock-error
inspection, and jj op log after unexpected state.