Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[v24.2.x] config: mark cloud_storage_enabled() as needs_restart::yes #23236

Merged
merged 1 commit into from
Sep 7, 2024

`config`: mark `cloud_storage_enabled()` as `needs_restart::yes`

bfde1ed
Select commit
Loading
Failed to load commit list.
Merged

[v24.2.x] config: mark cloud_storage_enabled() as needs_restart::yes #23236

`config`: mark `cloud_storage_enabled()` as `needs_restart::yes`
bfde1ed
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 8, 2024 in 0s

no rules match, no planned actions

⚠️ The pull request has been merged by @piyushredpanda

‼️ Action Required ‼️

The configuration uses the deprecated update_bot_account attribute of the queue action in one or more pull_request_rules. It must now be used under the queue_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

‼️ Action Required ‼️

**The configuration uses the deprecated speculative_checks attribute in the queue_rules section. It has been replaced in favor of max_parallel_checks in the merge_queue section 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
  • 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]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • 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 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

View more details on Mergify