GitHub Stacked PRs Kill the Graphite Moat
GitHub shipped stacked PRs natively and the developer reaction was immediate and enthusiastic. Multiple commenters noted they had been paying for Graphite specifically because stacked PR workflows were missing from GitHub, and that going back to stack-less GitHub after using Graphite felt painful.
The pattern: a third-party tool built a loyal user base by solving a real gap in GitHub's product, and GitHub eventually absorbed the feature. This is a recurring dynamic in dev tooling. The comments also flagged one remaining gap: stacking PRs across repositories is still not supported, leaving room for tools that work at the multi-repo level.
The discussion was largely positive, with early users reporting the feature works well for squash-merge workflows after a recent rebase improvement.
So what?
If you are building dev tooling that lives on top of GitHub, this is a reminder that GitHub will eventually ship the obvious stuff. The defensible position is either the workflow GitHub will never prioritize (cross-repo, enterprise-specific, niche language tooling) or deep integrations that go beyond what GitHub wants to maintain. Graphite still has a window, but it is narrowing.