[v24.2.x] [CORE-7039] schema_registry: Tolerate null metadata and ruleSet #23078
no rules match, no planned actions
The configuration uses the deprecated
update_bot_accountattribute of the queue action in one or morepull_request_rules. It must now be used under thequeue_rulesconfiguration.
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_checksattribute in thequeue_rulessection. It has been replaced in favor ofmax_parallel_checksin themerge_queuesection of the configuration.
For more information: https://docs.mergify.com/merge-queue/speculative-checks/
1 not applicable rule
Rule: enqueue on label (queue)
-
-closed[📌 queue requirement] -
base=dev -
label=merge-queue -
-conflict[📌 queue requirement] -
-draft[📌 queue requirement] - 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 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