GitHub stacked pull requests are generally available on all github.com plans: approvals survive rebases, whole stacks land via merge queue, and gh stack ships an AI-agent skill

Stacked pull requests are now GA on every github.com plan (GHES in an upcoming release), after a public preview that began on 2026-07-30. A stack is an ordered chain of branches: the bottom PR targets main, each PR above targets the branch below it, and reviewers see only the diff for that layer. This matters more as AI coding agents produce larger changes.

GA changes: Rebase stack keeps approvals on unchanged code, even in repos that dismiss stale approvals; replacement commits are signed and keep the original authorship, including automatic rebases after partial merges; users with bypass permission can merge the lowest unmerged PR; a stack enters and lands through the merge queue as a single merge group, and the merge-commit method now creates one merge commit per PR; stacks retarget automatically when their base branch is deleted; stack auto-merge rolls out over the coming weeks. The UI adds a persistent stack header, Shift+J/K navigation and timeline events, and the pull_request webhook gains a stacked action.

Numbers (GitHub's own): repos using stacks merge 9% more code than peers, and over two-thirds of the top 1% of repos use stacks, with a 5% faster time-to-merge. There is no independent benchmark.

Getting started: gh extension install github/gh-stack (gh v2.0+, Git 2.36+), then gh stack init, add, push and submit. v0.2.0 (2026-10-02) supports Git worktrees, and gh skill install github/gh-stack gives AI coding agents a ready-made skill for stacked workflows.