Match JJ Topology to Repo Role
VCS-MATCH-JJ-TOPOLOGY-TO-REPO-ROLE
Summary
Align fetch remotes, push remotes, tracked bookmarks, aliases, and PR bases to repo role. Owned, maintainer, and fork-only workflows need different topology assumptions.
Rule
Match jj remote topology to the repository role.
Why
Owned repos, maintainer-access repos, and fork-only contributor repos need different remote and
bookmark topology. Fetch remote, push remote, trunk(), tracked bookmarks, and PR base should match
the role instead of assuming GitHub's default names.
Helps
- Keeps local jj aliases and publication behavior aligned with the actual collaboration model.
Limits
Topology can be simple in personal repos. Reevaluate when the repo is forked, transferred, cloned
with gh, or used for contributor work without push access.
Agent Instruction
Match jj remote topology to the repository role because owned repos, maintainer-access repos, and
fork-only contributor repos need different remote and bookmark topology.Mechanisms
Supported by remote inspection, repo role notes, jj config get revset-aliases.trunk, tracked
bookmark checks, and explicit repair steps after user approval.