Aviator MergeQueue vs GitHub merge queue

High-performance, purpose-built merge queue keeps your builds green at scale

Start free trial today

or

Talk to a developer

Aviator MergeQueue is battle-tested and used by large engineering teams with various code-base configurations

Supports stacked PRs syncing and merging

Highly programmable and customizable with sensible defaults

Detailed Comparison

GitHub MQ

In-place update and merge

Parallel mode

Fast-forwarding (linear git history)

Batching

Multi-queue (affected targets)

PR dependencies within and across repos (change sets)

Natively integrated with GitHub

Flaky test support

Customize required checks

Wildcards required checks

Optimize CI runs

High priority merges

Custom actions

Stack aware merge queue

APIs for PR and queue status

Queue and dequeue APIs

Pause queue

Live Statistics API

GraphQL API (beta)

Webhooks

Slack Integration

Real-time support (enterprise)

SOC2 Type II compliance

Self-hosted

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

We offer a team-wide onboarding session to give your team a conceptual understanding of the product

Real-time help via a dedicated Slack channel for any needs that come up post setup

FAQs

How does Aviator MergeQueue 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 Aviator MergeQueue 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 I 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 is a "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? Contact us