gh-stack

Install the gh-stack extension with gh extension install github/gh-stack, then run gh stack init with branch names bottom to top. Commit each layer's changes on its branch and run gh stack submit --auto to push branches and open draft PRs.

Plan dependency-ordered layers before writing code, such as models, API, frontend, and tests. Create the stack first with gh stack init, commit each concern on its own branch, and submit the stack so reviewers see only each layer's diff.

Yes, but you must pass explicit flags because gh stack branches on whether stdout is a TTY. Use view --json, submit --auto, merge with --yes, and always provide branch names to init and add to avoid prompts or TUIs.

gh stack sync detects the squash merge and rebases remaining branches with --onto against the correct target, skipping the merged branch. No manual action is needed unless the replay conflicts, in which case run gh stack rebase and resolve.

This means the local stack and the GitHub stack have diverged, and non-interactive sync refuses to guess. Either keep the remote version with unstack --local then checkout, or keep the local version with unstack then submit --auto.

Stacks are strictly linear with one parent and at most one child, and there is no non-interactive reorder or removal since gh stack modify is TUI-only. Restructuring requires unstack followed by init, and gh pr merge cannot merge a stack.