GitHub adds native "Stacked PRs" — stack, review, land in one click

GitHub announced a native implementation of stacked pull requests: an ordered stack of PRs that can be reviewed as separate, focused layers and merged together with a single click. Each PR represents one slice of a larger change — small, reviewable, and easier to reason about — but lands atomically so repositories don’t end up half-finished. Simple on the surface. Potentially huge for teams wrestling with giant, tangled diffs.

How it works — and why reviewers will sigh with relief

Think of it like a patch series, but built into the GitHub UI. Authors arrange PRs into an ordered stack; reviewers inspect each layer independently; CI runs per-PR; and once everything is green and approved the stack is merged in order, end to end. That reduces noisy reviews and context-switching. It’s the sort of workflow long championed in Gerrit and by kernel maintainers — now packaged for mainstream repos and GitHub’s ecosystem. Want to break a sprawling refactor into bite-sized, reviewable commits? This is your tool.

What to watch

Stacked PRs will change habits fast: it’s a boon for readability and merge hygiene, but it also demands discipline — keep stacks small, rebase carefully, and make sure automation understands the dependency order. CI cost and merge semantics could trip up teams that treat stacks as magic bullets. Still, for anyone who’s ever stared at a gigantic monolith PR and felt that sinking feeling, this feels like a breath of fresh air. Will it kill the monster PR? Maybe not overnight — but it certainly blunts its teeth.

Sources: github.github.com, Hacker News