GitHub Launches Stacked Pull Requests to End 'Mega-PR' Bottlenecks

GitHub launched "stacked pull requests" into public preview on July 30, 2026, introducing a structural shift in how developers manage large-scale code changes. The feature allows engineers to decompose massive updates into a series of smaller, ordered, and interconnected pull requests—known as layers—which can be reviewed in parallel and merged in a single operation.

Each pull request in a stack targets the layer immediately below it, creating a logical chain of dependencies. To help reviewers navigate these dependencies, GitHub included a "stack map" at the top of each PR, providing a visual representation of how a specific layer fits into the broader set of changes. The tool is accessible across the GitHub ecosystem, including the web interface, the mobile app, and the GitHub CLI. Developers can also integrate the feature into coding agents like GitHub Copilot via the gh-stack skill. For those using the command line, the necessary extension is available through the command `gh extension install github/gh-stack`.

The End of the 'Mega-PR'

Traditionally, developers faced a difficult choice when implementing complex features: they could either submit one massive "mega-PR" that often overwhelmed reviewers, or manually manage a complex web of branches. The latter required tedious rebasing to keep branches synchronized, often slowing the development cycle. Stacked PRs automate this workflow by treating a sequence of individual PRs as a single logical unit, maintaining the granularity of small changes without the manual overhead of branch management.

Solving the AI Productivity Gap

This shift is critical as AI-generated code increases the volume of changes entering the pipeline. Andy Merryman, CTO of TED, noted that while AI has made developers dramatically more productive, it created a new bottleneck where PRs grew too large for reviewers to handle effectively. By breaking these changes into manageable chunks, teams can increase review accuracy and speed. Mayank Saini, a connectivity engineer at WHOOP, observed that large changes previously resulted in giant PRs that no one wanted to review, whereas stacks allow reviewers to follow a logical progression that merges in one shot.

Governance and Next Steps

Despite the streamlined merge process, GitHub has ensured that existing governance remains strict. Branch protections, required checks, and mandatory reviews remain intact and continue to govern what ultimately reaches the main branch.

Looking ahead, GitHub is progressively rolling out merge queue support for stacked pull requests in the weeks following the July 30 announcement. Tim Neutkens, NextJS lead at Vercel, stated that using the feature over the past few months has already helped his team introduce smaller individual changes while shipping larger features, signaling a broader move toward more modular code delivery.