Merge the current branch's commits into its parent branch. Children of the current branch become children of the parent. User input: $ARGUMENTS.

When to use

• Two adjacent branches turned out to be the same logical change and shouldn't be separate PRs.
• A small follow-up branch is ready to be rolled into the change it depends on.

Steps

1. Run gt ls and confirm the parent branch with the user. Ask for confirmation before folding — this is destructive on the PR for the disappearing branch name (close it manually or pass --close).
2. Run gt fold. By default the resulting branch keeps the parent's name.
   • gt fold --keep (-k) — keep the child's name instead, retiring the parent's name.
   • gt fold --close (-c) — also close the now-redundant PR.
3. Auto-restack runs for upstack branches. Resolve conflicts as usual.
4. gt submit --stack -u to push the surviving branch and the restacked upstack branches to their PRs.

Notes

• The folded branch now contains both sets of commits. Consider running /graphite:squash afterwards to keep the Graphite "one commit per branch" style.
• If you want the opposite — break a branch apart — use /graphite:split.