# GitHub makes stacked pull requests a native production workflow

GitHub's stacked pull requests have moved out of preview, giving teams a first-party way to split one dependent change into smaller reviewable layers while preserving repository checks and coordinated merging.

Stacked pull requests are now generally available on GitHub. The shift matters as coding agents make large changes faster than humans can safely review them: teams can keep one coherent change dependency-ordered while reviewing it as smaller PRs.

- Status: Active
- Published: 2026-10-07T14:13:32+13:00
- Updated: 2026-10-07T14:13:32+13:00
- Categories: Web Development, Developer Tools
- Tags: code review, developer workflow, GitHub, pull requests
- Canonical HTML: https://beyondthe.news/dossiers/github-stacked-pull-requests-ga-review-agent-code

## What changed

GitHub moved stacked pull requests from public preview to general availability on October 6. A stack represents a dependency-ordered series of pull requests for one larger change, letting reviewers inspect smaller focused diffs while GitHub tracks the relationship between layers. GitHub's async merge API, made generally available October 1, can merge stacked pull requests and is the recommended programmatic merge path; it is the only GitHub merge API that supports stacks.

## Why it matters

Large AI-assisted changes increasingly move the bottleneck from writing code to reviewing it. Native stacks let teams preserve dependency relationships without forcing reviewers through one giant diff or relying on an external stacking service. General availability removes the preview boundary for teams that want to standardise the workflow, while the async merge API gives automation a supported path for landing stacks.

## One change can stay coherent without becoming one giant PR

Each pull request in a stack represents a focused layer and depends on the layer below it. Reviewers can reason about smaller diffs while the overall change remains explicitly connected.

## The merge path is now programmable

GitHub's generally available async merge API supports individual and stacked pull requests, merge queues and permitted rules bypass. GitHub recommends it over the older synchronous REST endpoint or GraphQL mutations for programmatic merging.

## Agent-generated code makes review structure more important

Faster code generation does not remove human review constraints. Stacks provide a way to break agent-produced work into dependency-aware review boundaries instead of accepting a single oversized pull request.

## Key details

- GitHub stacked pull requests reached general availability on October 6, 2026.
- Stacks represent dependency-ordered pull requests for a larger change.
- GitHub's async merge API supports stacked pull requests and became generally available October 1.
- The async API is GitHub's recommended path for programmatic pull-request merging and the only merge API supporting stacks.

## Builder takeaways

- Use stacks when a large change has real dependency layers that can each form a coherent review unit.
- Keep each layer independently understandable and testable rather than using stacks to hide unrelated work.
- Automation that lands stacks should use GitHub's async merge API rather than older synchronous merge paths.
- For coding-agent workflows, design the agent's output around review boundaries instead of only optimising generation speed.

## What to watch

- Adoption of stacked PRs in agent-heavy development teams.
- Changes to gh-stack tooling and merge-queue behaviour after general availability.
- Whether GitHub exposes more stack-aware policy and analytics controls.

## Uncertainties

- The exact productivity effect depends on repository practices and change structure; general availability does not make stacking appropriate for unrelated work.
- Third-party workflow integrations may differ in how fully they understand stack relationships.

## Sources

- [Stacked pull requests generally available](https://github.blog/changelog/2026-10-06-stacked-pull-requests-generally-available) — GitHub · primary · 2026-10-06T00:00:00+13:00. Primary general-availability announcement consumed from BTN's discovery queue.
- [GitHub async merge API generally available](https://github.blog/changelog/2026-10-01-github-async-merge-api-generally-available/) — GitHub · primary · 2026-10-01T00:00:00+13:00. Primary documentation for programmatic stack merging and merge-queue support.