GitHub Invokes Spirit of Phabricator with Preview of Stacked PRs

Why It Matters

Stacked PRs streamline large code changes into incremental reviews, reducing bottlenecks and accelerating delivery for teams using GitHub’s platform. The capability also differentiates GitHub from competitors and offers a migration path for former Phabricator users.

Key Takeaways

• Stacked PRs let developers break large changes into smaller, reviewable units
• Each PR in a stack depends on its predecessor, enabling sequential merges
• GitHub offers an optional CLI, gh stack, for stack creation and management
• AI agents can use the CLI to automate review workflows
• Feature is in private preview, following Phabricator’s stacked diffs legacy

Pulse Analysis

Large pull requests have long been a pain point for software teams, inflating review time and increasing the risk of missed defects. By allowing a series of dependent pull requests, GitHub’s Stacked PRs revive the stacked‑diff concept pioneered by Facebook’s Phabricator, but embed it directly into the world‑wide platform that hosts the majority of open‑source code. The design forces developers to isolate logical units of work, turning monolithic changes into bite‑size reviews that can be merged independently. This granular approach aligns with modern CI/CD pipelines, where rapid, incremental integration is essential for maintaining velocity.

The feature ships in a private preview and can be accessed entirely through the web UI, preserving the familiar GitHub experience for most users. For power users and automation scripts, GitHub also provides the optional ‘gh stack’ command‑line extension, which mirrors the UI actions and can be invoked by AI agents or bots. By exposing stack metadata via the API, the CLI enables custom tooling to reorder, rebase, or batch‑merge stacks without manual intervention. This dual‑mode access lowers the barrier to adoption while offering the flexibility demanded by large engineering organizations.

From a market perspective, Stacked PRs give GitHub a competitive edge over rivals such as GitLab and Bitbucket, which currently lack native support for dependent pull requests. Enterprises that have migrated away from Phabricator for its discontinued roadmap now see a path to recapture that workflow without maintaining separate infrastructure. As code review remains the primary bottleneck in software delivery, the ability to parallelize reviews could translate into measurable productivity gains and faster time‑to‑market. Early feedback on Hacker News suggests strong developer enthusiasm, hinting at rapid broader rollout.