GitHub previews Stacked Pull Requests to end the 'mega-PR' bottleneck
The new native workflow lets developers break massive updates into ordered, reviewable layers to maintain code quality without manual branch overhead.
GitHub has launched a public preview of "Stacked Pull Requests," a native workflow designed to decompose large code changes into a series of smaller, ordered, and reviewable pull requests. The feature aims to solve a long-standing friction point in software development by allowing teams to maintain granular code quality without the manual overhead of managing dependent branches.
Launched on July 30, 2026, the system enables developers to create an ordered sequence of PRs where each subsequent layer targets the one below it. To help reviewers navigate these dependencies, GitHub added a "stack map" at the top of each PR, providing a visual representation of how a specific layer fits into the broader change. Users can initiate these stacks through github.com, the mobile app, AI agents like GitHub Copilot, or a dedicated CLI extension installed via `gh extension install github/gh-stack`.
The end of the 'mega-PR'
Traditionally, developers faced a binary choice when shipping large features: create a single, massive "mega-PR" that is overwhelming to review, or manually manage multiple dependent branches that require tedious rebasing. Stacked PRs formalize the latter approach within GitHub's native infrastructure. This allows teams to review logical chunks of a feature in parallel, increasing both the accuracy and velocity of the review process.
For high-velocity teams, the impact is immediate. Tim Neutkens, the Next.js lead at Vercel, noted that using the feature over the past few months has helped the team introduce smaller individual changes while shipping larger features. Similarly, Andy Merryman, CTO of TED, stated that while AI has made developers more productive, it created a new bottleneck where PRs grew too large for reviewers to handle—a problem Stacked PRs are designed to solve.
Industry implications and workflow
This shift is particularly critical as AI-assisted coding increases the volume of code generated. By breaking these outputs into manageable layers, GitHub is attempting to prevent the review process from becoming the primary bottleneck in the software development lifecycle. The efficiency extends to the merge process as well; users can merge the latest ready PR to land it and all unmerged layers beneath it in a single operation.
John Resig, the creator of jQuery, described the preview as "incredible," specifically highlighting the ability to land multiple stacked PRs directly to a merge queue simultaneously.
What to watch
As the feature moves through public preview, the focus will likely shift to edge-case stability and integration with existing merge strategies. While the core functionality is now available to the public, developers will be monitoring how the system handles complex squash-merges and whether the automation of dependent layers remains stable across diverse repository configurations.