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

• #approved-reviews-by>0
• approved-reviews-by=@flux-framework/core
• label="merge-when-passing"
• #changes-requested-reviews-by=0
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• -title~="^\[*(WIP|wip)"
• base=master
• label!="work-in-progress"
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • any of: [🛡 GitHub branch protection]
      • check-success = docs/readthedocs.org:flux-rfc
      • check-neutral = docs/readthedocs.org:flux-rfc
      • check-skipped = docs/readthedocs.org:flux-rfc
    • any of: [🛡 GitHub branch protection]
      • check-success = make check
      • check-neutral = make check
      • check-skipped = make check
    • any of: [🛡 GitHub branch protection]
      • check-success = validate commits
      • check-neutral = validate commits
      • check-skipped = validate commits

---

💖  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