Track Remotes Explicitly
VCS-TRACK-REMOTES-EXPLICITLY
Summary
Set explicit remote tracking when the same bookmark name exists on multiple remotes. This prevents fetch, rebase, and publication ambiguity in fork and upstream workflows.
Rule
Track remotes explicitly when bookmark names exist on multiple remotes.
Why
When the same bookmark name exists on multiple remotes, implicit tracking can choose the wrong source or make publication ambiguous. Explicit tracking tells jj which remote bookmark represents the local line of work.
Helps
- Prevents fetch, rebase, and publication confusion in fork and upstream workflows.
Limits
Single-remote repos may not need explicit repair after inspection confirms there is only one meaningful remote for the bookmark.
Agent Instruction
Track remotes explicitly for bookmark names that exist on multiple remotes so source and publication
targets are clear.Mechanisms
Supported by jj bookmark list --all-remotes, tracking commands, remote topology notes, and PR
base/head checks.