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

Clarify that spawning network in k8s should be in default namespace #1439

Draft
wants to merge 14 commits into
base: main
Choose a base branch
from

Merge branch 'main' into Update_docs_on_spawning_network_in_k8s

edc30f4
Select commit
Loading
Failed to load commit list.
Draft

Clarify that spawning network in k8s should be in default namespace #1439

Merge branch 'main' into Update_docs_on_spawning_network_in_k8s
edc30f4
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 25, 2024 in 8s

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 when CI passes on main (queue)

  • #approved-reviews-by>=1
  • -draft [📌 queue requirement]
  • label=automerge
  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue default]
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by=0
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • base=main
  • check-success=all
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

💖  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