Rule: Auto-update with merge if appropriately labeled (update)

• #commits-behind>0 [📌 update requirement]
• -closed [📌 update requirement]
• label=auto-update-merge
• -conflict
• -conflict [📌 update requirement]
• -draft

Rule: rebase-merge working updates (merge)

• -closed [📌 merge requirement]
• -conflict
• -conflict [📌 merge requirement]
• -draft
• -draft [📌 merge requirement]
• label=dependencies
• all of:
  • all of:
    • #commits-behind=0
    • #review-threads-unresolved=0
    • any of:
      • check-success=success
      • check-success=ci-cd / success
  • any of:
    • author=renovate[bot]
    • author=dependabot[bot]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed

Rule: ask to resolve conflict (comment)

• conflict

Rule: Auto-rebase if appropriately labeled or if the author is an authorized bot (rebase)

• -closed [📌 rebase requirement]
• -conflict
• -conflict [📌 rebase requirement]
• -draft
• any of:
  • all of:
    • label=dependencies
    • any of:
      • author=renovate[bot]
      • author=dependabot[bot]
  • label=auto-update-rebase

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com