3-5x
Mergify · published merge throughput gain
Mergify positions parallel testing and batching around a 3-5x merge throughput improvement.
Mergify merge queueCompare
How prmerger differs from the current category.
This page links to public category documentation from GitHub, Graphite, Mergify, and GitLab, then shows the product scope prmerger keeps.
Capability Matrix
Public category features on one table.
The table below compares documented category capabilities with prmerger's console scope.
| Capability | GitHub | Graphite | Mergify | GitLab | prmerger |
|---|---|---|---|---|---|
| Required-check aware queueing | Native merge queue | Queue settings plus GitHub protections | Queue rules and branch injection | Merge trains with pipelines | Visible in one readiness model before enqueue |
| Stack-aware merges | No stack model | Yes | Stack-aware batching | Sequential train order | Yes, with stack state shown next to the lane |
| Label-based enqueue | Not documented as core queue UX | Yes | Rule and command driven | Auto-merge / merge button | Yes, plus lane preview before action |
| Pause or incident control | Ruleset based | Queue settings | Pause, CLI, API | Manual train control | First-class pause, freeze, and recovery panel |
| Queue analytics | Limited in core UI | Operational status on PRs | Failure rate, queue size, retries, time to merge | Queue view and status | Built in as a default operator screen, not an add-on surface |
| Primary operator surface | Split across PRs, rules, and Actions | Split across PRs and queue tooling | Split across dashboard, config, and PR state | Split across merge requests and trains | Overview, queues, policies, and insights in one console |
Published metrics
60-90%
Mergify · published CI cost reduction
Mergify states that smart batching and queue execution can reduce CI cost by 60-90%.
Mergify merge queue20
GitLab · default parallel merge-train pipelines
GitLab documents a default maximum of 20 merge-train pipelines running in parallel before requests wait in line.
GitLab merge trainsmerge_group
GitHub · required queue event for protected checks
GitHub requires CI workflows to listen for merge_group when a merge queue is enforcing required checks.
GitHub merge queueprmerger product metrics
1
primary console
Overview, queues, policies, and insights sit in one product surface.
1
enqueue action
A ready pull request can enter a lane without another workflow step.
3
setup steps
Connect the app, map the rules, then open the lanes.
4
core views
Overview, queues, policies, and insights cover daily merge work.