Aviator MergeQueue vs Mergify

High performance battle tested merge queue to keep your builds green at scale

Our MergeQueue is battle-tested and hardened with teams of very large sizes and varioius code-base configurations

Supports stacked PRs syncing and merging

Highly programmable and customizable, with sensible defaults

Detailed Comparison

GitHub MQ
Parallel Mode
Fast Forwarding (linear git history)
Multi-queue (Affected Targets)
PR dependencies within and across repos (Change Sets)
Flaky test support
Customize required checks
Support conditional required checks
Support wildcards (*) for required checks
Optimize CI runs
High priority merges
Custom actions
Stack-aware merges and syncs
APIs for PR and Queue status
Queue and dequeue APIs
Base branch pause
Repository pause
Customizable Slack Integration
Real-time support (enterprise)
Aviator MQ

A personalized support that your team deserves

We’ll walk you through all necessary configurations to ensure that your MergeQueue is set up to work with your team’s specific infra and tooling.
A team-wide onboarding session to give them a conceptual understanding of the product
Real-time help via a dedicated Slack channel for any needs that come up post setup.


Have questions? We have answers
How does it work with GitHub and my CI provider?
Aviator connects to GitHub as a GitHub app that can then trigger actions on Pull Requests. Aviator also has CI plugins to pull information from your CI providers.
Does it work with self-hosted GitHub Enterprise?
Yes, Aviator offers a self-hosted version that can work with any public or self-hosted GitHub version.
How do you choose a merge strategy?
There are several configurations to optimize your merge strategy. Aviator walks you through some set up instructions when you sign up and generates a merge strategy. You can later customize the strategy as your needs evolve.
What do you mean by stack-aware merge queue?
Aviator also has an open source CLI for handling stacked PRs. This CLI is integrated with the Aviator MergeQueue to provide a seamless experience for syncing and merging stacked PRs.
How does Aviator MergeQueue handle flaky tests?
Aviator has built in merge strategies to handle flaky tests.  For instance you can specify optimistic_validation_failure_depth in our configuration to build in some resilience for flaky tests. There are also automatic reruns and automatic quarantining that you can setup using TestDeck.
Still haven’t found your answer. Talk to a developer

From startups to Fortune 500s, the worlds most effective engineering teams supercharge their developers with Aviator.

Let us show you how it works

Get started for free