Rule: automatic merge (merge)

• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• all of:
  • check-success=trigger_and_monitor_openqa
  • #check-failure=0
  • #check-pending=0
  • -label~=^acceptance-tests-needed|not-ready
  • base=master
  • linear-history
• all of:
  • #approved-reviews-by>=2
  • #changes-requested-reviews-by=0
  • #review-requested=0
• -closed [📌 merge requirement]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed

Rule: automatic merge on special label (merge)

• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• all of:
  • check-success=trigger_and_monitor_openqa
  • #check-failure=0
  • #check-pending=0
  • -label~=^acceptance-tests-needed|not-ready
  • base=master
  • linear-history
• all of:
  • label=merge-fast
  • base=master
• -closed [📌 merge requirement]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed

✅ Rule: ask to resolve conflict (comment)

• conflict

---

💖  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