The News, Explained

GitHub made stacked pull requests generally available on October 6, 2026. A stacked pull request workflow divides a large code change into a chain of smaller, dependent pull requests that can be reviewed separately and merged in order. The feature is available on every github.com plan and is planned for a future GitHub Enterprise Server release. Source

What changes during rebases and merges

A rebase reapplies a change on top of the latest base branch to bring its history up to date. Approvals now remain in place when a stack is rebased after its base branch, such as main, moves forward, as long as the reviewed code did not otherwise change. This also applies in repositories configured to dismiss stale approvals. Replacement commits created by GitHub during a stack rebase are signed and preserve the original authorship. Automatic rebases after partial merges also sign replacements when branch rules require signatures or any original commit was signed. Source

People who can bypass repository rules can use that permission when merging the lowest unmerged pull request in a stack. A merge queue manages the order of changes and checks the requirements for merging them. It treats a stack as one merge group. When a repository uses merge commits, GitHub creates one merge commit for each pull request instead of one for the entire group. If the base branch of a branching stack is deleted, GitHub retargets the stack instead of closing its bottom pull request. Source

Auto-merge, navigation, and automation

Auto-merge for stacks is rolling out over the next few weeks. A user can select a group of pull requests, and the group merges after every pull request satisfies the repository’s merge requirements. It is a phased rollout at the time of the announcement. Source

Stack details remain visible in the pull request page header. Shift+J and Shift+K move between pull requests in a stack, while timeline events show when a pull request joined or left the stack. The pull_request webhook adds a stacked action when a pull request joins a stack. The gh stack extension for GitHub CLI, which provides command-line access to GitHub, now supports Git worktrees and includes faster initialization, checkout, and navigation. A worktree lets people use separate working folders for different branches of one repository. Source

Results GitHub reported from public preview

GitHub says repositories using stacks during public preview merged 9% more code than peer repositories. More than two-thirds of repositories in the top 1% by activity now use stacked pull requests, and GitHub reported a 5% improvement in their time to merge. These are comparative figures reported by GitHub from its own service data. Source

OYOPICK’s Take

OYOPICK would judge a stack by how clearly it defines the scope of review, alongside the amount of code merged. Consider a hypothetical feature that changes how data is saved and adds a screen that uses it. One pull request can change the storage behavior, with the next adding the screen on top. Reviewers can examine each layer and the dependency between them separately. The example illustrates a hypothetical workflow; we have not measured time savings.

The new approval behavior applies when the reviewed code remains unchanged. Teams can distinguish a base-branch update from a feature-code change and focus another review where it is needed. GitHub’s 9% and 5% figures compare repositories; the announcement does not present a measurement isolating stacks as the cause. If small review units and visible dependencies continue to meet the repository’s merge requirements, changes built by developers and coding agents together could become easier for people to review in an understandable sequence.