Change information stored in _topic_node_index to avoid oversized alloc
#17350
Mergify / Summary
succeeded
Jul 27, 2024 in 1s
1 potential rule
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 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: enqueue on label (queue)
-
label=merge-queue - any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
dev]- any of: [🛡 GitHub repository ruleset rule]
-
check-neutral=bk-redpanda -
check-skipped=bk-redpanda -
check-success=bk-redpanda
-
-
#approved-reviews-by>=1[🛡 GitHub branch protection] -
#changes-requested-reviews-by=0[🛡 GitHub branch protection]
- any of: [🛡 GitHub repository ruleset rule]
- all of: [📌 queue conditions of queue
-
-draft[📌 queue requirement] -
base=dev - any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed -
check-success=Configuration changed
-
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