We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 16 since April 2026, each linked to its source.
gh-stackWhen a stack’s branches are spread across worktrees, use `gh stack rebase`, `gh stack sync`, or `gh stack modify`; gh-stack runs each change in the worktree owning its branch. If a rebase or modify pauses for conflicts, resolve and stage them in the reported checkout, then continue or abort from any worktree.
gh stack rebaseWhen `gh stack add` runs interactively on a branch outside a stack, accept its offer to initialize a stack; the supplied or generated branch name becomes the first layer.
gh stack add [branch]If the current branch or requested branch is not tracked locally but belongs to an active remote stack, run `gh stack checkout` or `gh stack checkout <branch>` and accept the prompt to check it out. The command imports the matching stack through the PR checkout flow; fully merged stacks are omitted. ([v0.1.1 release](https://github.com/github/gh-stack/releases/tag/v0.1.1))
gh stack checkoutIf merging the current stack or a selected stack or PR, run `gh stack merge` with the appropriate optional target. Choose the merge extent and method interactively, or use `--yes` or a non-interactive terminal with a method flag to merge without prompts; the operation is all-or-nothing.
gh stack mergeWhen adding a named branch, use its name directly; `gh stack add refactor/foo` creates that branch. To create a branch from a message, run `gh stack add -m "<message>"`; the v0.0.8 release says an omitted name generates `MM-DD-slug`.
gh stack add refactor/fooWhen you need to choose a stack without knowing its identifier, run `gh stack checkout` in an interactive terminal and select it from the picker. Use the All/Local/Remote tabs or `/` search; selecting a remote-only stack clones it locally before switching to it.
gh stack checkoutWhen checking out or unstacking a tracked stack by its GitHub UI number, use that number: run `gh stack checkout <stack-number>` to check it out or `gh stack unstack <stack-number>` to unstack it. Find the number in the GitHub UI or gh-stack output.
gh stack checkout <stack-number>When appending pull requests to an existing stack, run `gh stack link <stack-number> <pr-number-or-url> <branch-name>`; the stack number selects the target, and the remaining arguments are ordered bottom to top.
gh stack link 7 48 ui-polishWhen dissolving a stack that may not be tracked locally, run `gh stack unstack <stack-number>` from within the repository. It dissolves the stack through GitHub’s API and removes local tracking when present.
gh stack unstack <stack-number>When preparing PRs for a stack, run `gh stack submit` in an interactive terminal to choose branches, edit each PR’s title and description, and set ready or draft state. Submit the choices together with Ctrl+S.
gh stack submit