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

Changes the yaml for crd creation to remove deprecation warning on v1.22 #250

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

cleaned everything up

977ddc0
Select commit
Loading
Failed to load commit list.
Open

Changes the yaml for crd creation to remove deprecation warning on v1.22 #250

cleaned everything up
977ddc0
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jan 4, 2024 in 2s

4 potential rules

Rule: Automatically merge into master after build and review (queue)

  • #approved-reviews-by>=1
  • status-success=main
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-neutral=PR Title Checker (becomes a merge/squash commit)
        • check-skipped=PR Title Checker (becomes a merge/squash commit)
        • check-success=PR Title Checker (becomes a merge/squash commit)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=build
        • check-skipped=build
        • check-success=build
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [📌 queue requirement]
  • -mergify-configuration-changed [📌 queue -> allow_merging_configuration_change setting requirement]
  • base=master

Rule: Automatically merge into master after build and review (label)

  • #approved-reviews-by>=1
  • status-success=main
  • base=master

Rule: Automatically mergify-yaml changes to master (queue)

  • title~=^fix(mergify)
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-neutral=PR Title Checker (becomes a merge/squash commit)
        • check-skipped=PR Title Checker (becomes a merge/squash commit)
        • check-success=PR Title Checker (becomes a merge/squash commit)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=build
        • check-skipped=build
        • check-success=build
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [📌 queue requirement]
  • -mergify-configuration-changed [📌 queue -> allow_merging_configuration_change setting requirement]
  • base=master

Rule: Automatically mergify-yaml changes to master (label)

  • title~=^fix(mergify)
  • base=master
💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

4 not applicable rules

Rule: Automatically merge backport into release branches (queue)

  • author~=mergify
  • base~=^release-
  • head~=mergify/bp
  • status-success=main
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-neutral=PR Title Checker (becomes a merge/squash commit)
        • check-skipped=PR Title Checker (becomes a merge/squash commit)
        • check-success=PR Title Checker (becomes a merge/squash commit)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=build
        • check-skipped=build
        • check-success=build
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [📌 queue requirement]
  • -mergify-configuration-changed [📌 queue -> allow_merging_configuration_change setting requirement]

Rule: Automatically merge backport into release branches (label)

  • author~=mergify
  • base~=^release-
  • head~=mergify/bp
  • status-success=main

Rule: Automatically merge into release- after build and approval (queue)

  • #approved-reviews-by>=1
  • base~=^release-
  • status-success=main
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by>=1 [🛡 GitHub branch protection]
      • any of: [🛡 GitHub branch protection]
        • check-neutral=PR Title Checker (becomes a merge/squash commit)
        • check-skipped=PR Title Checker (becomes a merge/squash commit)
        • check-success=PR Title Checker (becomes a merge/squash commit)
      • any of: [🛡 GitHub branch protection]
        • check-neutral=build
        • check-skipped=build
        • check-success=build
      • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • -draft [📌 queue requirement]
  • -mergify-configuration-changed [📌 queue -> allow_merging_configuration_change setting requirement]

Rule: Automatically merge into release- after build and approval (label)

  • #approved-reviews-by>=1
  • base~=^release-
  • status-success=main
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