‼️ 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.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules

Rule: automatic merge (queue)

• #approved-reviews-by>=1
• check-success=test (py311, mysql-file)
• check-success=test (py311, mysql-file-sqlalchemy14)
• check-success=test (py311, mysql-s3)
• check-success=test (py311, mysql-swift)
• check-success=test (py311, postgresql-file)
• check-success=test (py311, postgresql-file-sqlalchemy14)
• check-success=test (py311, postgresql-file-upgrade-from-4.5)
• check-success=test (py311, postgresql-s3)
• check-success=test (py311, postgresql-swift)
• check-success=test (py312, mysql-ceph)
• check-success=test (py312, mysql-ceph-upgrade-from-4.5)
• check-success=test (py312, mysql-file)
• check-success=test (py312, mysql-file-sqlalchemy14)
• check-success=test (py312, mysql-s3)
• check-success=test (py312, mysql-swift)
• check-success=test (py312, postgresql-ceph)
• check-success=test (py312, postgresql-file)
• check-success=test (py312, postgresql-file-sqlalchemy14)
• check-success=test (py312, postgresql-file-upgrade-from-4.5)
• check-success=test (py312, postgresql-s3)
• check-success=test (py312, postgresql-swift)
• check-success=test (py39, mysql-ceph)
• check-success=test (py39, mysql-ceph-upgrade-from-4.5)
• check-success=test (py39, mysql-file)
• check-success=test (py39, mysql-file-sqlalchemy14)
• check-success=test (py39, mysql-s3)
• check-success=test (py39, mysql-swift)
• check-success=test (py39, postgresql-ceph)
• check-success=test (py39, postgresql-file)
• check-success=test (py39, postgresql-file-sqlalchemy14)
• check-success=test (py39, postgresql-file-upgrade-from-4.5)
• check-success=test (py39, postgresql-s3)
• check-success=test (py39, postgresql-swift)
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• check-success=check (build)
• check-success=check (pep8)
• check-success=doc (docs)
• check-success=doc (docs-gnocchi-web)
• label!=work-in-progress
• any of: [📌 queue -> configuration change requirements]
  • check-success = Configuration changed
  • -mergify-configuration-changed
• any of: [🔀 queue conditions]
  • all of [📌 queue conditions of queue default]

✅ Rule: dismiss reviews on additional commit (dismiss_reviews)

Rule: backport stable/4.5 (backport)

• label=backport-to-4.5
• merged [📌 backport requirement]

Rule: backport stable/4.6 (backport)

• label=backport-to-4.6
• merged [📌 backport requirement]

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

1 not applicable rule

Rule: automatic merge backports from Mergify (queue)

• base~=^stable/.*
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• author=mergify[bot]
• label!=work-in-progress
• any of: [📌 queue -> configuration change requirements]
  • check-success = Configuration changed
  • -mergify-configuration-changed
• any of: [🔀 queue conditions]
  • all of [📌 queue conditions of queue default]

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