Migrate from Bors‑NG to Mergify

Bors‑NG orchestrates a “try → staging → master” flow with batch testing and ordered merges. Mergify offers a production‑grade Merge Queue with similar guarantees plus flexible rules.

• Keep your branch protection and checks
• Define one queue rule in .mergify.yml
• Replace bors r+ approvals with @mergify queue command

• bors r+ approval → @mergify queue command
• batch size → Mergify batches with configurable size
• priority → Mergify queue priorities

Queue and rule that enqueue on approval and pass checks:

queue_rules:
  - name: default
    batch_size: 1
    queue_conditions:
      - base = main
      - check-success = ci
      - "#approved-reviews-by>=1"

If you relied on bors try to validate speculative changes, you can keep a lightweight CI workflow triggered by a label or comment

Increase throughput with batches and prioritize urgent PRs:

queue_rules:
  - name: default
    batch_size: 3
    queue_conditions:
      - base = main
      - check-success = ci
      - "#approved-reviews-by>=1"

priority_rules:
  - name: urgent
    conditions:
      - label = urgent
    priority: high