Merge Queue

Merge your pull request in the right order.

undraw_ideas_flow_cy7b.svg

Why needing a merge queue?

Safety

Do not merge broken pull requests. By merging your pull requests serially using a queue, your code is safe. Each pull request is tested with the latest CI code.

Prioritization

Makes sure that the important pull requests go first in the queue and are the first ones to be merged.

Save CI time

Rather than overconsuming your CI time by trying to merge multiple pull requests, just run it once before the pull request gets merged.

How it works

Define your rules

Write fine-grained conditions in your Mergify configuration. Define which checks are mandatory, the number of reviews required, etc., to get a pull request mergeable.

Enable Mergify

Write your rules in YAML. You can match a pull request on any criteria: branch, author, labels, etc.
Then uses the queue action to trigger a git merge as soon as the pull request is ready, setting the priority of the pull request.

See configuration file specification

Watch and merge!

Mergify updates the pull request status in real-time and informs you about which criteria match. As soon as your condition is validated, Mergify merges the pull request using the method you specified.

Get Started

Discover how Pitch leverage merge queues

Their main branch is always ready to be deployed to production.

Ready to get started?

Or check out our documentation for more details.