GitHub revives Phabricator, debuting stacked pull‑request previews for developers

GitHub’s Stacked PRs feature builds on a workflow that originated in Facebook’s internal Differential tool, later open‑sourced as part of Phabricator in 2011. As The Register notes, the concept of “stacked diffs” lets each pull request be based on the one immediately preceding it, forming a linear chain where every PR can be reviewed and merged independently so long as all lower‑level PRs have already been merged. This design directly addresses the classic problem of developers continuing work on a dependent branch while waiting for earlier changes to be approved, which historically forces large, monolithic pull requests that are difficult to review. By encouraging “smaller pull requests, which are therefore easier to review,” the documentation stresses that each branch in a stack should encapsulate a discrete logical unit of work (The Register).

Implementation in GitHub mirrors the Phabricator experience but adds a native UI path and an optional command‑line extension, gh stack. Sameen Karim, the engineer leading the effort, told LinkedIn that the CLI is “completely optional” and that users can create stacked PRs entirely through the web interface (The Register). The CLI, however, is intended to streamline the workflow for power users and for automated agents: “The stack CLI is also designed for use by AI agents,” Karim added (The Register). While some developers on Hacker News question the necessity of a dedicated CLI given recent Git enhancements that support similar behavior, the GitHub team argues that the built‑in UI and the specialized commands reduce friction and make the stacked‑diff pattern accessible to a broader audience (The Register).

From a technical standpoint, the bottom PR in a stack always targets the main branch, while each subsequent PR targets the head of the preceding PR. This ordering guarantees a deterministic merge order: the stack can be merged incrementally, or the entire chain can be merged in a single operation once all constituent PRs have passed review. The system enforces this dependency chain automatically, preventing a higher‑level PR from being merged before its ancestors, which eliminates the risk of integration conflicts that can arise when developers manually rebase or cherry‑pick dependent changes. According to the documentation, “Each pull request in the stack can be reviewed and merged independently, provided that all the pull requests below it in the stack are merged first” (The Register).

GitHub’s rollout of Stacked PRs also reflects a strategic response to the broader industry shift toward AI‑augmented development. Karim highlighted that the bottleneck in modern software delivery has moved from code authoring to code review, and that “Stacks help solve that” (The Register). By breaking large changes into granular, review‑friendly units, the feature not only speeds up human review cycles but also creates a more tractable target for AI‑driven code‑review assistants, which can operate on smaller diffs with higher precision. The inclusion of the gh stack CLI, designed for AI agents, suggests that GitHub envisions automated reviewers or bots generating and managing stacked PRs as part of continuous integration pipelines.

The revival of a Phabricator‑style workflow on GitHub arrives at a time when the original open‑source Phabricator project has been dormant since 2021, though its fork, Phorge, remains under active maintenance (The Register). Jackson Gabbard, a former Facebook engineer, observed that developers who have used Phabricator’s stacked‑diff workflow “generally love it and seek it wherever they next go” (The Register). By integrating this paradigm directly into the dominant Git hosting platform, GitHub is effectively re‑introducing a proven productivity boost to a much larger user base, potentially reshaping how large‑scale code changes are managed across the industry.