⚠️ The pull request has been merged by @tomwhite

‼️ Action Required ‼️

The configuration uses the deprecated merge_method attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_rules configuration.
A brownout is planned on September 16th, 2024.
This option will be removed on October 21st, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: automatic merge (queue)

• -closed [📌 queue requirement]
• #approved-reviews-by>=1
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• approved-reviews-by=@sgkit-dev/committers
• base=main
• label=auto-merge
• status-success=build (3.10)
• status-success=build (3.11)
• status-success=build (3.9)
• status-success=win_build (3.9)
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed
• any of: [🔀 queue conditions]
  • all of [📌 queue conditions of queue default]

✅ Rule: deleting merged branch (delete_head_branch)

• closed [📌 delete_head_branch requirement]
• merged

Rule: ping author on conflicts (comment, label)

• conflict

✅ Rule: remove conflict label if not needed (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