AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 14, 2026, 10:00 JST

GitHub ships Stacked pull requests to tame AI-sized code changes

GitHub ships Stacked pull requests to tame AI-sized code changes

3 Key Points

  1. What happened

    GitHub released Stacked pull requests in public preview on July 30, 2026 and made them generally available on October 6, letting teams split big changes into ordered, small PRs across github.com, GitHub CLI, the mobile app and Copilot via gh-stack.

  2. Why it matters

    AI agents now run long observe-plan-execute-evaluate loops that generate huge diffs, and GitHub reports more merged code and better time-to-merge in repos that used stacks during preview, suggesting small batches protect reviewers' attention.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The case for stacking small pull requests is not new — external tools such as Graphite and Sapling have offered stacked workflows for years. What changed is that AI coding agents, which run long loops of observing, planning, executing and evaluating, now produce large volumes of code changes at once, and a single giant diff forces reviewers to hold too much context in their heads. GitHub folding stacked PRs into the platform as a standard feature reads as an industry answer to that mismatch between how much code AI generates and how much a human can review at one time.

Google Cloud's DORA research program's 2025 "State of AI-assisted Software Development" report describes AI as an amplifier that magnifies an organization's strengths and weaknesses alike. DORA found AI adoption helps delivery throughput and product performance but remains linked to delivery instability, and interprets this as downstream weaknesses surfacing as AI speeds development up. Absent strong automated tests, mature version control and fast feedback loops, rising change volume tends to destabilize delivery.

Developer experience is a precondition for getting value from AI rather than a perk: fast CI, written-down implicit knowledge, and small review units are long-standing software engineering practices that now double as the conditions AI agents need to work well. GitHub's stacked-PR feature is one concrete piece of that groundwork.

FAQ
What are Stacked pull requests in GitHub?
They let you split a large change into an ordered series of small, reviewable pull requests, each targeting the one directly below it, instead of packing everything into one giant PR.
Where can I use Stacked pull requests?
On github.com, the GitHub CLI, and the mobile app, and through the gh-stack skill it is also usable from coding agents such as GitHub Copilot.
Did stacked PRs actually improve anything for GitHub users?
GitHub reports that during the preview, repositories using stacks saw more merged code and improved time-to-merge, though those are GitHub's own figures.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOpenAI engineer charged over alleged bug in exec room