Auto⁠-⁠Merge

Mergify can act on a pull request as soon as all applicable merge protection success_conditions are satisfied. The exact action (merge directly or add to the merge queue) depends on whether the merge queue is enabled for the repository.

Auto-merge is configured with the auto_merge_conditions field under merge_protections_settings. It accepts true for unconditional auto-merge, or a list of conditions to restrict the audience.

Set auto_merge_conditions: true to auto-merge every pull request that satisfies the merge protections:

merge_protections_settings:
  auto_merge_conditions: true

merge_protections:
  - name: require-review-and-ci
    if:
      - base = main
    success_conditions:
      - "#approved-reviews-by >= 1"
      - check-success = ci

Any pull request targeting main with at least one approved review and a passing ci check is automatically merged (or queued if the merge queue is enabled).

Pass a list of conditions to restrict auto-merge to pull requests that match. Only matching pull requests are auto-merged. Other pull requests still need to be merged manually or queued via the /queue command.

merge_protections_settings:
  auto_merge_conditions:
    - author = dependabot[bot]

The list accepts the same condition syntax as success_conditions, including nested and, or, and not operators.

auto_merge_conditions accepts:

• true: unconditional auto-merge.
• A list of conditions: conditional auto-merge.

The schema rejects false, null, and {} (an empty mapping). To disable auto-merge, omit the field entirely.

Auto-merge dependency updates from Dependabot, leaving every other pull request to be merged manually:

merge_protections_settings:
  auto_merge_conditions:
    - author = dependabot[bot]

Auto-merge any pull request that carries the ready-to-merge label:

merge_protections_settings:
  auto_merge_conditions:
    - label = ready-to-merge

queue_rules[].autoqueue is deprecated and will stop working on 2026-07-16. The replacement is auto_merge_conditions in merge_protections_settings.

Mergify opens an automatic migration pull request that rewrites the configuration. The translation depends on the shape of the original configuration:

• All queues had autoqueue: true: the migration produces auto_merge_conditions: true. Each queue’s existing queue_conditions still gate routing, so they don’t need to be duplicated.

• One autoqueued queue alongside manual queues: the migration inlines that queue’s queue_conditions into auto_merge_conditions.

• Multiple autoqueued queues alongside manual queues: the migration produces an or over each autoqueued queue’s conditions.

• Autoqueued queue with empty queue_conditions: collapses to auto_merge_conditions: true, since an empty list matches every pull request.

When a configuration mixes autoqueued and manual queues, the migration pull request includes a YAML comment listing the queues that remain manual-only. Those queues stay reachable via the /queue command.

Before:

queue_rules:
  - name: dependencies
    autoqueue: true
    queue_conditions:
      - author = dependabot[bot]
    merge_conditions:
      - check-success = ci

  - name: default
    queue_conditions:
      - check-success = ci

After:

queue_rules:
  - name: dependencies
    queue_conditions:
      - author = dependabot[bot]
    merge_conditions:
      - check-success = ci

  - name: default
    queue_conditions:
      - check-success = ci

merge_protections_settings:
  auto_merge_conditions:
    - author = dependabot[bot]

auto_merge_conditions only takes effect when at least one merge protection rule is configured. Without protection rules there are no success_conditions to evaluate.