Snapshot
Continue to About ↓- What it does
- Mergify is a pull-request automation service for GitHub built around a merge queue that tests batches of approved pull requests against the latest main branch before merging, so main stays green while more pull requests land.
More detail
- It also sells CI Insights (CI observability and automatic retry of failed jobs) and Test Engine (rerunning, retrying and quarantining flaky tests) as part of the same plan.
- Best for
- Platform and infrastructure teams on GitHub, especially monorepos with high pull-request volume, long CI runs or flaky tests.
More detail
- Regulated teams that need the product to run inside their own network can use Mergify Enterprise Server.
- Pricing
- Subscription priced per active contributor.
More detail
- Open Source is $0 for open source projects
- Free is $0 for private repos with up to 5 active contributors (24-hour CI job metrics, 7-day test metrics, 5 tracked branches).
- Max is $21 per seat per month in USD (list price, saving 15% on yearly billing) for
- Main limitation
- Teams on GitLab, Bitbucket or Azure DevOps: the published evidence covers GitHub and GitHub Enterprise Server only, and support for other platforms is not evidenced.
More detail
- Teams with low pull-request volume or short CI runs will see little benefit from batching and bisection.
- Record
- Living and monitored
- Reviewed
- Evidence
- Public web research
- Machine access
- Structured profile ↗
About
- Mergify is a pull-request automation service for GitHub built around a merge queue that tests batches of approved pull requests against the latest main branch before merging, so main stays green while more pull requests land.
- It also sells CI Insights (CI observability and automatic retry of failed jobs) and Test Engine (rerunning, retrying and quarantining flaky tests) as part of the same plan.
What it helps with
- Pull requests can land on main untested against what is already there, breaking the branch for everyone.
- Running CI separately for every pull request drives up CI load and cost as volume grows.
- When a batch fails, teams cannot quickly tell which pull request is the culprit.
- Flaky tests fail good builds and eject good pull requests from the merge process.
- Unrelated changes in a monorepo block each other in a single merge line.
- Manual merge coordination, ordering and hotfix prioritization consume engineering time.
- CI failures are opaque, so engineers guess at root causes and rerun jobs manually.
Capabilities
A practical view of what is available and where limitations apply.
| Offering | Available | Detail |
|---|---|---|
| Merge queue | Yes | Tests batches of approved pull requests against the latest main before merging. |
| Batching | Yes | Multiple pull requests share one CI run, reducing CI load. |
| Fail First bisection | Yes | Identifies the failing pull request in a batch so the others can continue. |
| Parallel lanes and scopes | Yes | Gives each part of a monorepo its own merge lane, using path or build-tool scopes. |
| Flaky test handling | Yes | Anti-flake protection, in-job retry and auto-quarantine keep flaky failures from blocking merges; containment is limited to flakes the engine identifies. |
| CI Insights | Yes | Job health, duration and failure-rate metrics, slowdown tracking, PR summary comments, Slack notifications and automatic job retry. |
| Merge controls | Yes | Priorities, merge freezes (scheduled or on-demand with hotfix exceptions), Depends-On and Merge-After, and stacked pull requests, configured via .mergify.yml. |
| On-premise deployment | Limited | Mergify Enterprise Server runs in the customer's network on GitHub Enterprise Server or GitHub.com; it is listed as an Enterprise-tier option. |
| SSO and delegated roles | Yes | Listed on the pricing page feature comparison; SOC 2 Type 2 is stated by the vendor and not independently verified here. |
| Non-GitHub platform support | Unknown | GitLab, Bitbucket and Azure DevOps are not evidenced in the supplied sources. |
Bot trust
How confidently AI systems can verify this profile from public evidence.
—of 100
ChatGPT—/100
Claude—/100
This profile has not completed a Bot Score assessment yet.
Evidence
Where this record came from, when it was reviewed, and how confidently it can be used.
- Verification
- Scribble researched these facts from the linked public sources.
- The owner has not manually confirmed every field.
- Last reviewed
- Primary source
- mergify.com
Technical profile details
Record ID
285f9c0e-48aa-4ada-b1bb-38511661b83eCanonical URLhttps://profiles.scribble.network/listing/mergify-285f9c0e