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

archival: skip spillover retention if not collectable #23358

Merged
merged 1 commit into from
Sep 18, 2024

archival: skip spillover retention if not collectable

26df815
Select commit
Loading
Failed to load commit list.
Merged

archival: skip spillover retention if not collectable #23358

archival: skip spillover retention if not collectable
26df815
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 18, 2024 in 1s

1 potential rule

⚠️ The pull request has been merged by @lf-rep

‼️ 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

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
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