Merge Queue Overview
Deterministic, parallel, and resource-aware merging for your team.
Mergify’s merge queue prevents broken main branches by ensuring every PR is tested against the latest code before merging. No more “it worked on my branch” failures.
What Mergify Solves
Section titled What Mergify SolvesBroken Main Branch
Section titled Broken Main BranchPRs that pass CI individually can break main when merged together. Mergify updates each PR against the latest main and re-runs CI before merging—catching conflicts before they hit production.
Slow Merge Throughput
Section titled Slow Merge ThroughputSerial testing creates bottlenecks. Mergify tests multiple PRs in parallel using speculative execution, so your queue moves as fast as your CI allows.
Spiraling CI Costs
Section titled Spiraling CI CostsRunning full test suites on every PR is expensive. Mergify batches PRs together into single CI runs and supports two-step CI to run heavy tests only at merge time.
→ Batches | Two-step CI
Monorepo Complexity
Section titled Monorepo ComplexityUnrelated changes shouldn’t block each other. Mergify uses scopes to identify which services a PR affects and only batches compatible changes together.
→ Scopes | Monorepo guide
Key Features
Section titled Key Features| Feature | What it does |
|---|---|
| Parallel checks | Test multiple PRs simultaneously |
| Batches | Combine PRs into single CI runs |
| Priority rules | Let urgent PRs jump the queue |
| Two-step CI | Run heavy tests only at merge time |
| Scopes | Smart batching for monorepos |
| Queue rules | Route PRs to different queues |
| Pause | Freeze merges during incidents |
Learn More
Section titled Learn More- Performance tuning — balance reliability, velocity, and cost
- Monitoring — track queue health and metrics
- Deployment strategies — roll out safely to your team