Skip to content

Press

Writing about Mergify? Everything on this page is free to copy and quote. No need to ask.

About Mergify

The paragraph to drop at the bottom of an article or a press release.

Mergify helps engineering teams ship faster without breaking main. Its merge queue, CI Insights, and test management tools automate the path from pull request to production, so CI stays fast and reliable without getting expensive. Thousands of organizations, from startups to public companies, merge with confidence on Mergify.

Company at a glance

The basics, in a form you can paste straight into a fact box.

Founded
2018
Headquarters
Toulouse, France
Founders
Julien Danjou (CEO) and Mehdi Abaakouk (CTO)
Funding
Bootstrapped, no outside capital raised
Used by
2k+ organizations
Products
Merge Queue, CI Insights, Test Engine
Works with
GitHub and any CI provider

Fast facts: State of Merge Queues 2026

Findings from our analysis of 200,000 merges. Each line stands on its own, so you can quote any of them.

  • Mergify analyzed more than 200,000 pull requests merged across 477 engineering organizations over a rolling 90-day window (State of Merge Queues 2026).
  • AI-assisted pull requests broke the main branch 1.9% of the time, against 4.4% for pull requests with no detectable AI assistance.
  • Broken-main rates rose roughly 16x with team size: about 1 in 130 merges at 2 to 5 engineers per repository, and 1 in 8 at 40 or more.
  • At least 1 in 7 pull requests in private repositories is AI-assisted, and that is a floor: assistants that leave no trace on the commit are invisible to the measurement.
  • Private repositories broke the main branch 4.5x more often than open source, and 94% of teams still merge one pull request at a time instead of batching.

Cite as: Mergify, "State of Merge Queues 2026," mergify.com/reports/state-of-merge-queues-2026. Data licensed CC BY 4.0.

Product screenshots

Full-resolution captures of the Mergify dashboard. Credit them to Mergify.

Merge Queue in the Mergify dashboard

Merge Queue

Download
CI Insights in the Mergify dashboard

CI Insights

Download
Test Engine in the Mergify dashboard

Test Engine

Download

Founders and origin story

How Mergify started, as told on our about page. Quote any of it.

Julien Danjou and Mehdi Abaakouk did not start from a business plan. They started from OpenStack, Debian, and Python: projects where hundreds of people push to the same branch and one bad merge costs everybody their afternoon. Julien had been a Debian developer since 2002 and both had years of OpenStack commits behind them, so the afternoon being lost was usually their own. Those communities had already solved it. Zuul and Bors did the same job in different places: no change landed on the main branch until CI had tested it there. Both came as a bot you had to run and keep alive yourself.

Most engineering teams have better things to do than operate a merge bot. So in May 2018, a few weeks after the first commit, Mergify started rebasing and merging pull requests one at a time, so nothing landed on main without being tested against what was already there. By October it had ordering and priorities. The engine was open source back then, and those commits still carry their 2018 dates.

That is the whole origin story. No pivot, no rebrand. The founders wanted what those projects had, for everybody else, and Mergify was the first to sell it.

Julien Danjou, Founder & CEO of Mergify

Julien Danjou

Founder & CEO

Mehdi Abaakouk, Founder & CTO of Mergify

Mehdi Abaakouk

Founder & CTO

Press contact

For an interview or a question about the data, email jd@mergify.com. Logos and usage guidelines are on the brand page.