GitHub merge queue alternatives.

Merget, Mergify, Graphite, Trunk and Aviator are alternatives to GitHub’s merge queue. They differ most in what happens when pull requests conflict: Merget resolves the conflict in queue order instead of sending the pull request back.

Merget resolves the conflicts other merge queues send back.

FeatureMergetGitHub merge queueMergifyGraphiteAviator
Resolves merge conflicts in the queueYesNoMechanical conflicts only, in PreviewNoNo
Finds conflicts Git merges cleanly, before CI runsYesNoNoNoNo
Who fixes a conflictThe queueThe authorThe author, unless it is mechanicalThe authorThe author
Orders and tests pull requests before they landYesYesYesYesYes
Batches pull requests for CIYesYesYesYesYes

From each vendor’s public documentation, checked November 13, 2026: GitHub, Mergify, Graphite, Aviator.

What each merge queue’s documentation says about conflicts.

Merge queueWhat it handlesWhen changes conflict
MergetCode analysis across open pull requests, conflict resolution and coordinated landing.Resolves the conflict in queue order, using the definitions, callers and behavior of the pull requests ahead. Checks the fix before landing through your required checks and reviews. What it cannot resolve safely returns to a person. How it works.
GitHub merge queueNative queueing and required checks against the target branch plus queued changes.Removes a pull request when it conflicts with the base branch or fails required checks. GitHub documentation.
MergifyConfigurable queueing and batching, plus Conflict Resolution, a Preview feature available on request.Its resolvers merge mechanical conflicts by structure: lockfiles, changelogs and source files such as Python imports and functions. The same line changed two ways, or a function both pull requests rewrote, goes to a person, and an unresolved pull request leaves the queue. Mergify documentation.
GraphiteStack-aware queueing, parallel CI and batching.Rebases stacked changes; a pull request with failing checks or merge conflicts is removed from the queue. Queue overview and using the queue.
TrunkQueue validation and retries for some transient failures.For a merge conflict that prevents a test branch, its documented recovery is to resolve the conflict by rebasing or merging the target, then requeue. Trunk documentation.
Aviator MergeQueueTests queued changes together before merging them into the target branch.Reports failures such as a failed required check and removes the pull request from the queue. Aviator documentation.

Vendor behavior checked against the linked documentation on November 13, 2026. Configuration matters; this compares documented workflows, not a performance test of these products.

A queue can find a failing combination. Merget also fixes it.

Merge queues test pull requests against the changes ahead of them. That protects a busy main branch. When the combination fails, someone still has to understand the conflict and write the fix, and with coding agents that someone is usually another agent run and another round of CI.

Merget puts that work inside the merge queue. Its PR graph follows definitions, callers and behavior across branches, so it also sees a semantic conflict, a conflict in meaning: one pull request renames a function while another adds a call to its old name, even though Git merges the text.

Deterministic rules resolve known conflict shapes and a coding agent handles harder ones. Every resolution is checked before it is used. See the resolution workflow or the conflict resolution benchmark.

Merget is its own merge queue. It does not depend on GitHub’s.

Any repository

Public and private, on GitHub.com

Install the GitHub App for an organization or a personal account and choose the repositories.

Joining

No enqueue command

Pull requests join the queue without a label or comment. Branch protection is optional.

Stacks

Stacked pull requests as they are

No stacking tool is needed, at any depth.

Control

Start in Advisory

Review findings while Merget changes no source code. Add resolution and landing per repository.

Choosing a merge queue for GitHub.

What are some alternatives to GitHub’s merge queue?

Merget, Mergify, Graphite, Trunk and Aviator are alternatives to GitHub’s merge queue. Each queues and tests pull requests before they reach the target branch; they differ in batching, stacking and what happens when pull requests conflict.

Is GitHub’s merge queue enough?

It can be. If native queueing and your CI already cover your workflow, GitHub’s merge queue may be all you need. If parallel agents keep returning to rebase and repair each other’s pull requests, that is the work Merget is built to take on. How GitHub’s merge queue works.

Does Mergify resolve merge conflicts?

Partly. Mergify’s Conflict Resolution is a Preview feature that merges mechanical conflicts, such as lockfiles and changelogs, by structure. Its documentation says the same line changed two ways, or a function both pull requests rewrote, still goes to a person.

Which merge queue is built for AI coding agents?

Merget is built for pull requests from parallel coding agents. Agents raise the number of pull requests that collide, so Merget resolves those conflicts in queue order and works on independent groups in parallel. Merge queue for AI coding agents.

Can I use Merget on a branch that uses GitHub’s merge queue?

Yes, with manual merging. On a branch that uses GitHub’s native merge queue, Merget still prepares pull requests and you merge through GitHub’s queue. To let Merget land work itself, remove GitHub’s merge queue rule from that branch.

How do I try Merget?

Sign up, install the GitHub App on one repository and review the findings in Advisory mode. Book a call if you want to walk through your current queue first.