✅ Rule: assign and label scala-steward's PRs (label)

• author=scala-steward

Rule: merge Scala Steward's PRs (merge)

• -closed [📌 merge requirement]
• status-success=build
• any of: [🛡 GitHub branch protection]
  • check-neutral = build
  • check-skipped = build
  • check-success = build
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• author=scala-steward
• base=master
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

Rule: automatic merge on CI success and review (delete_head_branch)

• #approved-reviews-by>=1
• status-success=build
• #changes-requested-reviews-by=0
• #review-requested=0
• base=master
• closed [📌 delete_head_branch requirement]

Rule: automatic merge on CI success and review (merge)

• #approved-reviews-by>=1
• -closed [📌 merge requirement]
• status-success=build
• any of: [🛡 GitHub branch protection]
  • check-neutral = build
  • check-skipped = build
  • check-success = build
• #changes-requested-reviews-by=0
• #review-requested=0
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• base=master
• any of: [📌 merge -> 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