Rule: Automatic merge on approval and successful build (delete_head_branch)

• status-success=build
• status-success=package-dotnet
• status-success=package-go
• status-success=package-java
• status-success=package-js
• status-success=package-python
• #approved-reviews-by>=1
• -label~=(do-not-merge)
• closed [📌 delete_head_branch requirement]

Rule: Automatic merge on approval and successful build (queue)

• status-success=build
• status-success=package-dotnet
• status-success=package-go
• status-success=package-java
• status-success=package-js
• status-success=package-python
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • any of: [🛡 GitHub branch protection]
      • check-neutral=build
      • check-skipped=build
      • check-success=build
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
• #approved-reviews-by>=1
• -draft [📌 queue requirement]
• -label~=(do-not-merge)
• -mergify-configuration-changed [📌 queue -> allow_merging_configuration_change setting requirement]

---

💖  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