Mergify covers the path from pull request to green main branch: a merge queue that tests each change against the code it will merge into, CI Insights for slow and failing jobs, and Test Engine for flaky tests.
Get started
Documentation
Talk to our team
Website · Pricing · Customers · Changelog · Blog · Status
Every plan includes all three.
Mergify tests each pull request on top of the latest main and the pull requests queued ahead of it, and merges it only when CI passes on that combined state. Two changes that each pass CI on their own can no longer break main together.
- Batching with bisection. One CI run validates several pull requests. When a batch fails, Mergify splits it to find the change responsible.
- Two-step CI. Fast checks decide which pull requests enter the queue, and the full suite runs once, right before the merge.
- Scopes. Independent parts of a monorepo merge in parallel lanes, defined from your build graph or from file patterns.
- Merge control. Scheduled freezes,
Depends-On:dependencies across repositories,Merge-After:scheduled merges, and GitHub stacked pull requests landed in order.
Coming from GitHub's merge queue? The comparison covers the differences and the migration.
CI Insights tracks every CI job and runner, shows which ones are slow, failing or flaky, and automatically retries jobs that failed for a transient reason.
Test Engine runs inside the test framework you already use, including pytest, Jest, RSpec, Vitest, Playwright and JUnit. It reruns the tests a pull request adds or changes to catch flaky ones before they merge, and quarantines known-flaky tests so their failures stop blocking merges.
- Mergify Cloud is operated by Mergify. Install the GitHub App and the queue is running.
- Mergify Enterprise Server runs the full product on your own infrastructure, with GitHub Enterprise Server or GitHub.com, for teams whose code cannot leave their network.
- Install the Mergify GitHub App.
- Comment
@mergifyio queueon an open pull request. Mergify updates it on top of main, runs your existing CI and merges it once CI passes. No configuration file is needed for this step. - Add a
.mergify.ymlto tune the queue. This one batches up to five pull requests per CI run and keeps the expensive suite for the final check:
queue_rules:
- name: default
batch_size: 5
batch_max_wait_time: 5 min
queue_conditions:
- check-success = quick-tests
merge_conditions:
- check-success = full-suiteThe documentation covers every option, and mergify config validate
from the Mergify CLI checks a configuration before it lands.
More than 2,000 organizations and 25,000 users work with Mergify every day, across 300,000 repositories. Engineering teams at Mozilla, Elastic, Cerebras, Back Market and PayFit describe how they run it in their own words, and the rest are on the customer stories page.
Mergify is SOC 2 Type II attested and does not store repository contents: for a git operation such as a rebase, it clones the repository into a temporary directory and deletes it when the operation finishes. Configuration and metadata are encrypted at rest with AES-256 and in transit with TLS 1.2 or higher. Authentication and permissions are delegated to GitHub, so a user's role in Mergify is their role on the repository.
- Trust Center: audit reports and the sub-processor list.
- Security documentation: data handling and each permission the GitHub App requests.
- HackerOne: vulnerability reports, through the bug bounty program.
- security@mergify.com: Data Processing Addendum requests.
- Documentation for setup guides and the configuration reference.
- support@mergify.com, or Help Center › Contact us in the dashboard, for anything that blocks you.
- Mergifyio/mergify for public bug reports and feature requests.
- Slack community for questions to the team and other users.
- status.mergify.com for availability and incident history.
Mergify publishes its command line and CI integrations from this organization:
| Repository | Purpose |
|---|---|
| mergify-cli | The mergify command: stacked pull requests, merge queue status, test result uploads and configuration validation. Holds the releases and the issue tracker. |
| setup-cli | GitHub Action that installs a pinned version of the CLI. |
| gha-mergify-ci | GitHub Action that uploads JUnit results and detects merge queue scopes. |
| mergify-ci-buildkite-plugin | The same for Buildkite. |
| mergify-pre-commit | pre-commit hook that validates Mergify configuration files. |
Mergify has run merge queues in production since 2018. It is built by a small remote team across France and the Netherlands.
