Manage stacked PRs with Graphite CLI (gt) instead of git for branch/PR operations. Auto-detects Graphite repos via .git/.graphite_repo_config. Use when: creating stacked PRs, navigating branches, submitting PRs, syncing with main, restacking after changes, or any gt command usage.
Use Graphite CLI (gt) instead of raw git for all branch and PR operations in Graphite-initialized repos.
A repo is Graphite-initialized if .git/.graphite_repo_config exists. When detected, prefer gt over git for branch/PR workflows.
The Graphite MCP server (gt mcp) is available. Use the learn_gt and run_gt_cmd tools when available:
learn_gt — look up gt command documentationrun_gt_cmd — execute gt commands directlyPR #3 (top)
|
PR #2
|
PR #1
|
main (trunk)
| Command | Description |
|---|---|
gt checkout [branch] | Switch branches (interactive picker if no arg) |
gt co main | Switch to trunk |
gt up [steps] | Navigate to child branch |
gt down [steps] | Navigate to parent branch |
gt top | Jump to top of stack |
gt bottom | Jump to trunk-closest branch |
| Command | Description |
|---|---|
gt create -a -m "message" | Create new branch with staged changes |
gt c --no-interactive -m "message" | Create new branch (non-interactive) |
gt modify --no-interactive | Amend current commit |
gt m --no-interactive | Short form: amend current commit |
gt modify -a | Amend with staged changes, then restack |
gt modify --commit -a -m "msg" | Add explicit commit (for review feedback) |
gt delete [name] | Delete branch and metadata |
gt rename [name] | Rename branch |
| Command | Description |
|---|---|
gt restack | Rebase dependent branches after changes |
gt sync --no-interactive | Pull latest main, delete merged branches, rebase |
gt fold | Merge branch into its parent |
gt split | Break branch into multiple branches |
gt squash | Consolidate commits in branch |
gt reorder | Reorder branches in stack |
gt move --onto <branch> | Move branch to different parent |
| Command | Description |
|---|---|
gt submit --no-interactive | Push and create/update PR for current branch |
gt s --no-interactive | Short form: submit current branch |
gt s --stack --no-interactive | Submit current + all descendant branches |
gt ss | Alias for gt submit --stack |
gt s --draft --no-interactive | Submit as draft PR |
gt submit --reviewers alice,bob | Assign reviewers |
| Command | Description |
|---|---|
gt log / gt l | Show stack visualization |
gt log short / gt ls | Abbreviated stack view |
gt pr [branch] | Open PR in browser |
gt info [branch] | Display branch details |
| Command | Description |
|---|---|
gt continue | Resume halted operation (after conflict resolution) |
gt abort | Cancel current operation |
gt undo | Revert last operation |
| Instead of... | Use... |
|---|---|
git checkout -b branch | gt c --no-interactive -m 'message' |
git push | gt s --no-interactive |
git rebase main | gt restack |
git commit --amend | gt m --no-interactive |
git pull origin main | gt sync --no-interactive |
| Situation | Action |
|---|---|
| On main? | Never commit to main. Create new branch: gt c --no-interactive -m 'message' |
| On a branch + changes are related WIP? | Amend in place: gt m --no-interactive |
| On unrelated branch + independent changes? | gt co main then create new branch |
| On a branch + changes depend on it? | Create stacked branch: gt c --no-interactive -m 'message' |
--no-interactiveAll gt commands that support it should use --no-interactive to avoid blocking on prompts. Key commands:
gt c --no-interactive -m 'message'gt m --no-interactivegt s --no-interactive or gt s --stack --no-interactivegt sync --no-interactivegit diff)git add <specific-files>Use semantic commit names: feat:, fix:, chore:, refactor:, docs:, test:
gt s --draft --no-interactivegt s --no-interactivegt s --stack --no-interactive# During restack, if conflicts occur:
# 1. Resolve conflicts in the files
# 2. Stage resolved files
git add <resolved-files>
# 3. Continue the operation
gt continue
gt log shows the correct stack structure# Start from trunk
gt co main
gt sync --no-interactive
# Create first PR
# ... make changes ...
git add <specific-files>
gt c --no-interactive -m 'feat: add database migration'
# Create second PR on top
# ... make changes ...
git add <specific-files>
gt c --no-interactive -m 'feat: add backend service'
# Create third PR on top
# ... make changes ...
git add <specific-files>
gt c --no-interactive -m 'feat: add frontend components'
# Submit entire stack
gt s --stack --no-interactive
# Verify
gt log
# Navigate to the PR that needs changes
gt checkout branch-name
# Make changes, stage them
git add <specific-files>
# Amend and restack all branches above
gt m --no-interactive
# Push updates for the whole stack
gt s --stack --no-interactive