Rule: label-documentation (label)

• any of:
  • files~=^[^/]+\.md$
  • files~=^docs/
  • files~=^examples/
• -closed
• label != stale

Rule: ping author on conflicts and add 'needs-rebase' label (comment, label)

• conflict
• -closed
• label != stale

✅ Rule: remove 'needs-rebase' label when conflict is resolved (label)

• -closed
• -conflict

✅ Rule: auto-rebase if approved, ready, and 5 commits behind main (rebase)

• #approved-reviews-by >= 1
• #commits-behind >= 5
• -closed
• -closed [📌 rebase requirement]
• -conflict
• -conflict [📌 rebase requirement]
• -draft
• base = main
• label != stale
• queue-position = -1 [📌 rebase requirement]
• any of:
  • #commits-behind > 0 [📌 rebase requirement]
  • -linear-history [📌 rebase requirement]

Rule: add quality-failed label (comment, label)

• check-failure ~= ^quality-checks
• -closed
• label != stale

✅ Rule: remove quality-failed label (label)

• -check-failure ~= ^quality-check
• -closed
• label != stale

---

💖  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