Rule: Automatic squash and merge when CI passes and reviews approve (merge)

• -closed [📌 merge requirement]
• #approved-reviews-by >= 1
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
• #commits-behind = 0 [🛡 GitHub branch protection]
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• -label=do-not-merge/hold
• -label=wip
• branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
• check-success=Chart checks
• check-success=Codegen
• check-success=DCO
• check-success=Go build
• check-success=Go gateway test e2e (6, latest, ubuntu-22.04)
• check-success=Go gateway test e2e (6, v1.19.16-k3s1, ubuntu-20.04)
• check-success=Go gateway test e2e (6, v1.21.14-k3s1, ubuntu-22.04)
• check-success=Go gateway test e2e (6, v1.23.17-k3s1, ubuntu-22.04)
• check-success=Go gateway test e2e (7, latest, ubuntu-22.04)
• check-success=Go gateway test e2e (7, v1.19.16-k3s1, ubuntu-20.04)
• check-success=Go ingress test e2e (10)
• check-success=Go mesh test e2e (1, ubuntu-22.04)
• check-success=Go mesh test e2e (2, ubuntu-22.04)
• check-success=Go mesh test e2e (3, ubuntu-22.04)
• check-success=Go mesh test e2e (4, ubuntu-22.04)
• check-success=Go mesh test e2e (5, ubuntu-22.04)
• check-success=Go mesh test e2e (v1.19.16-k3s1, Test traffic flowing from client to server with a Kubernetes Ser...
• check-success=Go mesh test e2e (v1.27.16-k3s1, Test traffic flowing from client to server with a Kubernetes Ser...
• check-success=Go retry test e2e (9)
• check-success=Go statefulset test e2e (8)
• check-success=Go test
• check-success=Integration Test with Tresor, SMI traffic policies, and egress disabled
• check-success=Lint
• check-success=Mocks
• check-success=Scan images for security vulnerabilities
• check-success=Shellcheck
• any of:
  • base~=^release\/v
  • base=main
• any of:
  • all of:
    • label=ok-to-merge
    • label=squash
  • label=ok-to-squash
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [📌 merge requirement]
  • check-success = Mergify Merge Protections
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
• any of: [🛡 GitHub branch protection]
  • check-success = Codegen
  • check-neutral = Codegen
  • check-skipped = Codegen
• any of: [🛡 GitHub branch protection]
  • check-success = Go build
  • check-neutral = Go build
  • check-skipped = Go build
• any of: [🛡 GitHub branch protection]
  • check-success = Shellcheck
  • check-neutral = Shellcheck
  • check-skipped = Shellcheck
• any of: [🛡 GitHub branch protection]
  • check-success = Lint
  • check-neutral = Lint
  • check-skipped = Lint
• any of: [🛡 GitHub branch protection]
  • check-success = Chart checks
  • check-neutral = Chart checks
  • check-skipped = Chart checks
• any of: [🛡 GitHub branch protection]
  • check-success = DCO
  • check-neutral = DCO
  • check-skipped = DCO
• any of: [🛡 GitHub branch protection]
  • check-success = Mergify Merge Protections
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections

Rule: Cherry-pick patches from release/v* to the main branch (backport)

• label = cherry-pick/main
• base~=^release\/v
• merged [📌 backport requirement]

Rule: Ping PR author when conflicting and Label conflicting pull requests (comment, label)

• -closed
• conflict

Rule: Comment when a pull request has unverified commits (comment)

• #commits-unverified > 0
• -closed

---

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

🚀  You can help us by becoming a sponsor!

---

3 not applicable rules

Rule: Backport features/patches to the release/v1.4 branch (backport)

• base=main
• label = backport/v1.4
• merged [📌 backport requirement]

Rule: Backport features/patches to the release/v1.3 branch (backport)

• base=main
• label = backport/v1.3
• merged [📌 backport requirement]

Rule: Backport features/patches to the release/v1.2 branch (backport)

• base=main
• label = backport/v1.2
• merged [📌 backport requirement]

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