Redis: Fix sentinel fallbacks with IPv6 address #1374
Merged
Mergify / Summary
succeeded
Aug 20, 2024 in 3s
1 rule matches and 4 potential rules
The configuration uses the deprecated
merge_methodattribute of the queue action in one or morepull_request_rules. It must now be used under thequeue_rulesconfiguration.
A brownout is planned on August 26th, 2024.
This option will be removed on September 23rd, 2024.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
### Rule: automatic merge (queue)
-
check-success=test (py39, mysql-ceph) -
check-success=test (py39, mysql-ceph-upgrade-from-4.4) -
check-success=test (py39, postgresql-ceph) -
#approved-reviews-by>=1 -
-draft[📌 queue requirement] -
check-success=check (build) -
check-success=check (pep8) -
check-success=doc (docs) -
check-success=doc (docs-gnocchi-web) -
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.4) -
check-success=test (py311, postgresql-s3) -
check-success=test (py311, postgresql-swift) -
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-file) -
check-success=test (py39, postgresql-file-sqlalchemy14) -
check-success=test (py39, postgresql-file-upgrade-from-4.4) -
check-success=test (py39, postgresql-s3) -
check-success=test (py39, postgresql-swift) -
label!=work-in-progress - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of [📌 queue conditions of queue
default]
- all of [📌 queue conditions of queue
✅ Rule: dismiss reviews on additional commit (dismiss_reviews)
Rule: backport stable/4.4 (backport)
-
label=backport-to-4.4 -
merged[📌 backport requirement]
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)
-
author=mergify[bot] -
base~=^stable/.* -
-draft[📌 queue requirement] -
label!=work-in-progress - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
- any of: [🔀 queue conditions]
- all of [📌 queue conditions of queue
default]
- all of [📌 queue conditions of queue
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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
Loading