Rule: Automatic merge on approval (merge)

• -closed [📌 merge requirement]
• status-success=e2e (2.13.10)
• status-success=e2e (3.2.1)
• status-success=test (openjdk@1.11, 2.13.10)
• status-success=test (openjdk@1.17, 2.13.10)
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• author=paoloboni
• status-success=test (openjdk@1.11, 2.12.17)
• status-success=test (openjdk@1.11, 3.2.1)
• status-success=test (openjdk@1.17, 2.12.17)
• status-success=test (openjdk@1.17, 3.2.1)
• title~=^Update\s.*
• 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