Mergepatrol

Mergepatrol vs Graphite's merge queue

Graphite is a code review tool built around stacked pull requests, and its merge queue is one part of it. Mergepatrol is a merge queue on its own: it works with GitHub’s pull requests as they are, including stacks made with gh stack. Checked against Graphite’s docs and pricing on 31 October 2026.

At a glance

Graphite merge queueMergepatrol
PriceOn the Team plan ($40 a seat a month, billed annually) as a “Basic” queue, “Advanced” on Enterprise; not listed on Hobby or StarterPublic repos free; private repos $15 a seat a month after a 14-day trial; self-hosted free
What you adoptGraphite’s review app, and its gt CLI for stacksA GitHub App and a config file; review stays on GitHub
StacksStack-aware; a queued stack is validated in parallelA gh stack stack is one queue item, merged all at once with GitHub’s asynchronous merge
BatchingIn private beta; a failed batch is bisected or every PR isolatedOn by default; a failed batch is split in half down to the PR that broke it
A PR that conflictsRebased automatically, but a real conflict goes back to you to gt restack and re-queueA plain git rebase first, then an agent on a real conflict, checked by your verify commands
A required check that failsBack to its authorAn agent commits a fix on the PR, up to fix_ci.attempts times
Works alongside GitHub’s merge queueNo: GitHub’s queue must be offNo: one queue per branch
SourceProprietary SaaSApache-2.0, self-hostable

Where Graphite is the better fit

Where Mergepatrol is the better fit

FAQ

Do I need the Graphite CLI to use its merge queue? You can queue from Graphite’s web app, but its docs note that automatic restacking does not work when merging from GitHub.

Does Mergepatrol need gh stack? Only for stacks. A pull request stacked by hand on another PR’s branch is held; a gh stack stack queues as one item. Plain pull requests need nothing.