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
Re-parent the current branch onto a different branch and bring its descendants along. User input: $ARGUMENTS.
gt ls to show the current shape.$ARGUMENTS includes --onto <branch> or just a branch name, use that.gt move to open the interactive parent picker. If the session is non-interactive, ask the user for the target branch.gt move --onto <target-branch>.gt add . → gt continue -a, or gt abort.gt ls to confirm the new structure.-o, --onto <branch> — target parent (skips interactive picker)--only — move just this branch; do not bring children alonggt move --onto./graphite:reorder (editor-based)./graphite:create with --insert.