SNACK: 3-line summary
- GitHub’s stacked pull requests are now generally available on every github.com plan.
- Developers can review dependent changes in smaller pull requests, then merge them together.
- Stack auto-merge rolls out over the next few weeks; GitHub Enterprise Server support is planned for a future release.
GitHub’s stacked pull requests let developers break a large code change into smaller pieces, review each separately and merge them together. A pull request asks for a proposed code change to be reviewed; a stack connects requests that depend on one another.
Snackgirls react
AIKO: I’d want to trace the dependency chain before diving into the code. Finding the smallest useful review unit sounds like an interesting puzzle.
Nea: I’d like to understand one change before moving to the next. That sounds more inviting than scrolling through a long diff and trying to keep every detail in mind.
Follow the dependencies one request at a time
GitHub announced general availability on October 6. In a stack, one pull request can use another request’s branch as its base, keeping dependent changes connected. Stack details stay visible in the pull request page’s persistent header as reviewers move between the pieces.
When using a merge queue, the stack enters and lands as a single merge group. With the merge commit method, GitHub now creates one merge commit per pull request instead of one for the entire group.
Keep approvals when unchanged code is rebased
When a base branch such as main moves forward, Rebase stack now preserves approvals if the stack’s code is otherwise unchanged. That includes repositories that normally dismiss stale approvals.
Rebase stack also creates signed replacement commits while preserving the original authorship. After a partial merge, automatic rebases sign replacement commits when branch rules require signatures or any original commit was signed.
Who can use stacks now
Stacked pull requests are available on all github.com plans, with GitHub Enterprise Server support coming in an upcoming release. Stack auto-merge will roll out over the next few weeks: selected pull requests will merge together once every request meets the repository’s merge requirements.
More information: GitHub Changelog — https://github.blog/changelog/2026-10-06-stacked-pull-requests-generally-available (checked October 7, 2026).
Sources and checked date: October 7, 2026
Comments
0No login needed. Edit or delete your comment from the same browser.
All comments 0
한국어 · English · 日本語No comments yet. Start the conversation.