Fix an oversized alloc in cluster_config schema endpoint #23773
1 potential rule
The configuration uses the deprecated
update_bot_account
attribute of the queue action in one or morepull_request_rules
. It must now be used under thequeue_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
**The configuration uses the deprecated
speculative_checks
attribute in thequeue_rules
section. It has been replaced in favor ofmax_parallel_checks
in themerge_queue
section of the configuration.
For more information: https://docs.mergify.com/merge-queue/speculative-checks/
Rule: enqueue on label (queue)
-
-closed
[📌 queue requirement] -
label=merge-queue
-
-conflict
[📌 queue requirement] -
-draft
[📌 queue requirement] -
base=dev
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success = Configuration changed
-
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
dev
]-
#approved-reviews-by >= 1
[🛡 GitHub branch protection] -
#changes-requested-reviews-by = 0
[🛡 GitHub branch protection] - any of: [🛡 GitHub repository ruleset rule]
-
check-success = bk-redpanda
-
check-neutral = bk-redpanda
-
check-skipped = bk-redpanda
-
-
- 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 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