Rule: rebase and merge when passing all checks (queue)

• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
    • #approved-reviews-by>0
    • approved-reviews-by=@chaos/diod-admins
    • label="merge-when-passing"
    • any of: [🛡 GitHub branch protection]
      • check-neutral = build (clang, ubuntu-latest)
      • check-skipped = build (clang, ubuntu-latest)
      • check-success = build (clang, ubuntu-latest)
    • any of: [🛡 GitHub branch protection]
      • check-neutral = build (gcc, ubuntu-latest)
      • check-skipped = build (gcc, ubuntu-latest)
      • check-success = build (gcc, ubuntu-latest)
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0
    • -title~=^\[*[Ww][Ii][Pp]
    • base=master
    • label!="work-in-progress"
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

---

💖  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