Skip to content
New issue

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

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

Already on GitHub? # to your account

chore(dependencies): Autobump clouddriverVersion #2163

Merged

chore(dependencies): Autobump clouddriverVersion

23afaeb
Select commit
Loading
Failed to load commit list.
Merged

chore(dependencies): Autobump clouddriverVersion #2163

chore(dependencies): Autobump clouddriverVersion
23afaeb
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jun 14, 2024 in 2s

2 rules match and 5 potential rules

Rule: Automatically merge on CI success and review (queue)

  • approved-reviews-by=@oss-approvers
  • label=ready to merge
  • -draft [📌 queue requirement]
  • base=master
  • status-success=build
  • 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=build
        • check-neutral=build
        • check-skipped=build

Rule: Automatically merge on CI success and review (label)

  • approved-reviews-by=@oss-approvers
  • label=ready to merge
  • base=master
  • status-success=build

Rule: Automatically merge PRs from maintainers on CI success and review (queue)

  • label=ready to merge
  • -draft [📌 queue requirement]
  • author=@oss-approvers
  • base=master
  • status-success=build
  • 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=build
        • check-neutral=build
        • check-skipped=build

Rule: Automatically merge PRs from maintainers on CI success and review (label)

  • label=ready to merge
  • author=@oss-approvers
  • base=master
  • status-success=build

✅ Rule: Automatically merge autobump PRs on CI success (queue)

  • -draft [📌 queue requirement]
  • author:spinnakerbot
  • base~=^(master|release-)
  • label~=autobump-*
  • status-success=build
  • 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=build
        • check-neutral=build
        • check-skipped=build

✅ Rule: Automatically merge autobump PRs on CI success (label)

  • author:spinnakerbot
  • base~=^(master|release-)
  • label~=autobump-*
  • status-success=build

Rule: Request reviews for autobump PRs on CI failure (request_reviews)

  • status-failure=build
  • base=master
  • base~=^(master|release-)
  • label~=autobump-*

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


2 not applicable rules

Rule: Automatically merge release branch changes on CI success and release manager review (queue)

  • approved-reviews-by=@release-managers
  • base~=^release-
  • label=ready to merge
  • -draft [📌 queue requirement]
  • status-success=build
  • 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=build
        • check-neutral=build
        • check-skipped=build

Rule: Automatically merge release branch changes on CI success and release manager review (label)

  • approved-reviews-by=@release-managers
  • base~=^release-
  • label=ready to merge
  • status-success=build
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