chore(deps): update dependency rules_proto to v7 #606
Merged
Mergify / Summary
succeeded
Nov 15, 2024 in 1s
1 rule matches and 1 potential rule
The configuration uses the deprecated
merge_method
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_rules
configuration.
This option will be removed on January 31st, 2025.
For more information: https://docs.mergify.com/configuration/file-format/#queue-rules
Rule: merge using the merge queue (queue)
-
-closed
[📌 queue requirement] -
label=merge-queue
-
#approved-reviews-by>=1
-
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
base=master
-
check-success~=Build & Test - Examples \(.*\)
-
check-success~=Build & Test - Nixpkgs - .*
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success = all_ci_tests
-
check-neutral = all_ci_tests
-
check-skipped = all_ci_tests
-
-
- all of: [📌 queue conditions of queue
✅ Rule: remove from merge-queue after merge (label)
-
merged
💖 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
Loading