PROVIDER - Stacked pull requests and merge queues

Graphite

Graphite splits large changes into small stacked pull requests chained into 1 review path, with the gt CLI for committing and reordering, deep GitHub integration and a merge queue removing 80% or more of conflict re-runs; the gaps are the learning model and GitHub focus.

Developer Tools United States 2026.11.19
3.9pts

Detailed Notes

Pros 5 items

Splits large changes into several small pull requests chained into 1 review path with stacked diffs
Ships the gt CLI, which commits, reorders and edits any pull request inside a stack in 1 command
Integrates deeply with GitHub so 1 view shows the status of an entire stack
Adds a merge queue that removes 80% or more of conflict-driven re-runs
Offers a free tier for individuals and small teams, so 1 person can adopt stacking alone

Cons 4 items

The conceptual model needs team-wide learning, raising onboarding cost
Centred on GitHub with limited support for other hosts
Team analytics and similar capabilities need paid plans
Adopting it in existing large repositories requires process changes

Service Overview

Graphite is a code review and merge platform built around stacked pull requests, breaking large changes into independently reviewable slices.

In the development tools category it is review process tooling: it targets long review cycles on huge PRs and repeated merge conflicts.

Key Strengths

  • Stacked review: big changes in small steps
  • CLI friendly: gt manages the stack
  • Clear interface: whole stack in 1 view
  • Merge queue: fewer conflict re-runs
  • Individual friendly: free tier to start

Product Ecosystem

Platform capabilities

Stack management, automatic rebasing, pull request status views, merge queues, review rules and checks integration plus team review analytics.

Integrations

Integrates deeply with GitHub and works with GitHub Actions, Slack and mainstream IDE extensions.

Typical scenarios

Landing large refactors step by step, multi-person review collaboration, CI queue optimisation and commit granularity governance.

Limitations

  • Learning cost: the workflow needs practice
  • Platform coupling: GitHub first
  • Paid tiers: analytics need a subscription
  • Adoption effort: legacy repo processes shift

Use Cases

  • Landing large refactors (★★★★★): stacking shines
  • CI queue optimisation (★★★★☆): merge queue delivers
  • Tiny personal projects (★★☆☆☆): may be overkill
  • GitLab-first teams (★☆☆☆☆): not yet covered

Pricing

Item Price Notes
Free $0 Basics for individuals and small teams
Team Monthly per seat Merge queue and analytics
Enterprise Contact sales Compliance, SSO and support

FAQ

What are stacked pull requests?

One feature split into dependent small PRs reviewed and merged in order.

Is the CLI required?

No, the web UI works too; the CLI suits high-frequency users.

Does it support GitLab?

GitHub integration is currently the most complete.

What does the merge queue do?

It merges in order and re-runs checks automatically, reducing manual rebasing and conflicts.

Code Examples

# Install and authenticate
brew install withgraphite/tap/graphite
gt auth --token <YOUR_TOKEN>

# Create branches and commits to form a stack
gt branch create feat-part-1 -m "part 1: schema"
gt commit create -m "add orders table"

gt branch create feat-part-2 -m "part 2: api"
gt commit create -m "add orders endpoint"

# Submit the stack and inspect its state
gt stack submit
gt log short
# Sync with the remote and rebase the whole stack
gt sync

Community & Resources

Visit Graphite Website → https://graphite.dev/
Visit Website ↗