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.

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

Another nil check fix in BlockStorageProviderSuite #3160

Merged
merged 1 commit into from
Sep 25, 2024

Another nil check fix in BlockStorageProviderSuite

dd79d1f
Select commit
Loading
Failed to load commit list.
Merged

Another nil check fix in BlockStorageProviderSuite #3160

Another nil check fix in BlockStorageProviderSuite
dd79d1f
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 25, 2024 in 1s

1 rule matches and 1 potential rule

‼️ Action Required ‼️

The configuration uses the deprecated merge_method 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: Automatic merge (queue)

  • -closed [πŸ“Œ queue requirement]
  • -conflict [πŸ“Œ queue requirement]
  • -draft [πŸ“Œ queue requirement]
  • all of:
    • #approved-reviews-by>=1
    • base=master
    • check-success=build (controller)
    • check-success=build (kanctl)
    • check-success=build (kando)
    • check-success=docs
    • check-success=gomod
    • check-success=lint
    • check-success=test (helm-test)
    • check-success=test (integration-test)
    • check-success=test (test)
    • label!="hold off merging"
    • label=kueue
  • any of: [πŸ“Œ queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [πŸ”€ queue conditions]
    • all of: [πŸ“Œ queue conditions of queue default]
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = Summary
        • check-neutral = Summary
        • check-skipped = Summary
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = gomod
        • check-neutral = gomod
        • check-skipped = gomod
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = lint
        • check-neutral = lint
        • check-skipped = lint
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = test (test)
        • check-neutral = test (test)
        • check-skipped = test (test)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = test (helm-test)
        • check-neutral = test (helm-test)
        • check-skipped = test (helm-test)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = test (integration-test)
        • check-neutral = test (integration-test)
        • check-skipped = test (integration-test)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = docs
        • check-neutral = docs
        • check-skipped = docs
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = dependency-review
        • check-neutral = dependency-review
        • check-skipped = dependency-review
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = build (controller)
        • check-neutral = build (controller)
        • check-skipped = build (controller)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = build (kanctl)
        • check-neutral = build (kanctl)
        • check-skipped = build (kanctl)
      • any of: [πŸ›‘ GitHub branch protection]
        • check-success = build (kando)
        • check-neutral = build (kando)
        • check-skipped = build (kando)

βœ… Rule: delete head branch after merge (delete_head_branch)

  • closed [πŸ“Œ delete_head_branch requirement]
  • merged

πŸ’–Β Β Mergify is proud to provide this service for free to open source projects.

πŸš€Β Β You can help us by becoming a sponsor!


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