GitHub brings stacked pull requests to public preview for smaller code reviews

GitHub has moved stacked pull requests into public preview, adding a native way for developers to split a large change into a sequence of smaller, dependent pull requests without leaving GitHub's normal review workflow.

The feature is aimed at a familiar bottleneck in modern software teams: a single broad pull request can be hard to review, but manually maintaining a chain of branches can create its own operational overhead. GitHub says stacks are ordered pull requests in which each layer targets the one below it. Reviewers can inspect one layer at a time, while the stack map on the pull request page shows how that review fits into the larger change.

What changes for teams

In the preview, teams can create and manage stacks from github.com, the GitHub CLI, GitHub Mobile, or through coding-agent workflows that use the gh-stack skill. GitHub says existing reviews, checks, merge requirements, and branch protections continue to apply, which matters for organizations that already depend on GitHub as the system of record for code review and release controls.

The merge behavior is also designed for incremental adoption. A team can merge an entire ready stack in one operation, or land lower layers first while higher layers remain open and are automatically rebased and retargeted. That should make the feature useful for large refactors, feature work split across multiple services, and AI-assisted development sessions that can produce more code than reviewers want to evaluate in one oversized pull request.

• Stacked pull requests are rolling out to all repositories over the coming days.
• Merge queue support for stacked pull requests is planned to roll out progressively over the coming weeks.
• The initial workflow includes a GitHub CLI extension for creating a first stack from the terminal.

The launch is a product-level change rather than a new programming framework, but it could affect day-to-day engineering practice across many teams because pull requests are where quality checks, security gates, and peer review converge. By making stacked review a first-party GitHub workflow, the company is trying to reduce the friction that previously pushed teams toward third-party tools or branch-management conventions.

Sources

• github.blog

Cover photo by Nimit Kansagra on Pexels, used under the Pexels License.