Rule: CI automerge when passing all test (merge)

• -closed [📌 merge requirement]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• base=master
• check-success=CodeQL
• check-success=docs-build (3.12)
• check-success=macOS-latest (3.12)
• check-success=test-ubuntu (3.10)
• check-success=test-ubuntu (3.11)
• check-success=test-ubuntu (3.12)
• check-success=test-ubuntu (3.13)
• check-success=test-ubuntu (3.9)
• check-success=test-windows (3.12)
• label=ready-to-merge
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

✅ Rule: CI automerge when passing all test (comment, label)

• base=master
• check-success=CodeQL
• check-success=docs-build (3.12)
• check-success=macOS-latest (3.12)
• check-success=test-ubuntu (3.10)
• check-success=test-ubuntu (3.11)
• check-success=test-ubuntu (3.12)
• check-success=test-ubuntu (3.13)
• check-success=test-ubuntu (3.9)
• check-success=test-windows (3.12)
• label=ready-to-merge

Rule: Information about conflicts pull request (comment, label)

• 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