Stacked PR workflow with the Graphite CLI (gt) — create stacks, submit, sync, restack, split/squash/fold, track existing branches, collaborate on shared stacks, configure repo/CI for Graphite, and operate the merge queue.
70
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Bring branches that were created outside Graphite under gt's control by recording their parent. User input: $ARGUMENTS.
git checkout -b and Graphite doesn't know its parent.git fetch (not gt get).gt metadata was corrupted and needs to be re-established.git branch --show-current to confirm the branch under cursor.$ARGUMENTS starts with --untrack or is -u, run gt untrack <branch> and stop.gt track (will prompt for parent if ambiguous).gt track <branch>.gt track --force.gt track — it walks up until it hits an already-tracked branch.git rebase on tracked branches afterwards — it can remove the base commit Graphite uses to identify the branch's start. If you must rebase, use gt modify --interactive or gt restack.gt track complains about diverged parent, run git rebase <parent> once to align the branch on its parent, then gt track again.-p, --parent <branch> — set parent explicitly (skip the prompt)-f, --force — pick the nearest ancestor as parent automatically (useful for multi-branch tracking)