Stacked PRs
Stacked PRs are an ordered chain of small, dependent pull requests, each a reviewable layer of one larger change, that merge together once every layer passes. The pattern predates GitHub's involvement by years, popularized by Phabricator's Differential and, more recently, Graphite and Aviator.
GitHub built the workflow natively: a private preview shipped April 13, 2026 via the open-source `gh-stack` CLI, and public preview followed July 30, 2026 with a built-in stack map UI, one-click cascading merges, and a dedicated Copilot skill that makes the agent a first-class stack participant.
Next.js lead Tim Neutkens told GitHub: "We've been using GitHub stacked PRs for Next.js for the past few months. It has helped us introduce smaller individual changes while shipping larger features, making it easier to review PRs."
Like inspecting each floor of a building as it's poured, then handing over the finished tower in one closing.
See nascent terms 7 days before everyone, unlock every stage filter, and get weekly early alerts.
Why is it emerging now?
GitHub turned a decade-old third-party workflow into a native feature: private preview April 13, 2026, public preview July 30 — with Copilot as a first-class stack participant, directly pressuring Graphite and Aviator's stacking-only business model.
Search Interest
-
Nascent0–7 days
-
Emergent8–30 days
-
Validating31–90 days
-
Rising ← now91–180 days
-
Established180 days +
Outlook
6-month signal projection and commercial timeline.
Native GitHub distribution reaches every repo instantly; merge-queue parity over the next two quarters would erode Graphite and Aviator's core pitch.
Risk · GitHub calls it public preview with acknowledged rough edges; a stalled or scrapped rollout would leave the third-party tools' moat intact.
Analogs · GitHub Actions · GitHub Codespaces · merge queue
-
nowPublic preview, free, rough edges
gh-stack live for every repo; GitHub advises testing on low-stakes repos first.
-
3-6moMerge queue parity lands
Rolling out merge-queue support could close Graphite's remaining gap.
-
6-12moGA decides Graphite's moat
General availability determines whether paid stacking tools keep enterprise share.
Competition & Opportunity for term “Stacked PRs”
Signals derived from the tracked queries, the term's monetization cards, and its cluster neighbors. Heuristic except where marked measured (Google KD).
Ideas for term “Stacked PRs”
Buildable pitches — turn this term into an article, site, product, post, newsletter, video, or course. Steal any card and run with it.
No quality comparison exists yet. Cover native gh-stack vs Graphite's merge queue, VS Code extension, and $20/user pricing.
Step-by-step CLI tutorial. Feature is days old in public preview; almost no hands-on guides exist.
Explainer for the search-intent gap between 'what is a stacked PR' and GitHub's specific native implementation.
Coding agents still emit single large diffs; a splitter tool targets teams adopting AI agents plus native stacking together.
GitHub's stack map only lives in the web UI and mobile app; editor-native visualization is an open gap.
First-person migration story capturing the exact decision teams are weighing right now.
Short YouTube walkthrough targeting devs who just saw the changelog post and want a fast demo.
A venture-funded startup built its pitch on a gap GitHub closed with one CLI extension and a changelog post.
Phabricator's Differential had this in the 2010s. Copilot's unreviewable 2,000-line diffs are what finally forced GitHub's hand.
GitHub wired gh-stack directly into Copilot as a skill — because an autonomous agent's single massive commit is unreviewable at any size.
What People Search
Long-tail queries from Google Suggest + Trends. Volume and competition are heuristics — directional, not audited. Content Type comes from query shape.
SERP of term “Stacked PRs”
What searchers see today — organic results on top, paid ads if anyone's bidding. Ad density is a real-time commercial signal.
FAQ
What is Stacked PRs?
Stacked PRs are an ordered chain of small, dependent pull requests, each a reviewable layer of one larger change, that merge together once every layer passes.
Why is Stacked PRs emerging now?
GitHub turned a decade-old third-party workflow into a native feature: private preview April 13, 2026, public preview July 30 — with Copilot as a first-class stack participant, directly pressuring Graphite and Aviator's stacking-only business model.
When did Stacked PRs emerge?
Publicly emerged around 2026-04-13 (about 120 days ago as of 2026-08-11). EarlyTerms first recorded a pipeline signal on 2026-08-01.
Related Terms
Other terms in the same space — aliases, subtypes, competitors, and neighbors to explore next.
- Related copilot-sdk Copilot SDK is GitHub's multi-language library for embedding the Copilot agent runtime — planning, tool invocation, file editing, and… →
- Related local-merge-queue A local merge queue is a lightweight tool that serializes commits from several parallel coding agents onto one trunk branch, testing… →
- Related open-code-review Open Code Review is a hybrid-architecture CLI for AI-assisted code review: deterministic pipelines handle file filtering, rule matching,… →
- Related coding-agents Coding Agents is the category name for AI developer tools that act on code autonomously — reading a repo, planning a change, editing… →
- Also known as
- Competitor
- Related
Sources
Primary URLs this report cites — open any to verify the claim yourself.
- 01 GitHub Changelog — Stacked pull requests now in public preview github.blog ↗
- 02 GitHub Docs — About stacked pull requests docs.github.com ↗
- 03 Hacker News — GitHub Stacked PRs (private preview reveal) news.ycombinator.com ↗
- 04 Hacker News — Stacked PRs are now live on GitHub news.ycombinator.com ↗
- 05 Agent Wars — GitHub Ships Stacked PRs, Graphite Feels the Heat agent-wars.com ↗
- 06 InfoQ — GitHub Targets Large Merge Problem with Stacked PRs infoq.com ↗
- 07 github/gh-stack repository github.com ↗
- 08 explainx.ai — GitHub Stacked Pull Requests, Public Preview (July 2026) explainx.ai ↗