Rule: backport patches to v0.52.x branch (backport)

• base=main
• label=backport/v0.52.x
• merged [📌 backport requirement]

Rule: backport patches to v0.50.x branch (backport)

• base=main
• label=backport/v0.50.x
• merged [📌 backport requirement]

Rule: backport patches to v0.47.x branch (backport)

• base=main
• label=backport/v0.47.x
• merged [📌 backport requirement]

Rule: backport patches to v0.46.x branch (backport)

• base=main
• label=backport/0.46.x
• merged [📌 backport requirement]

Rule: backport patches to v0.45.x branch (backport)

• base=main
• label=backport/0.45.x
• merged [📌 backport requirement]

Rule: automerge to main with label automerge and branch protection passing (queue)

• -closed [📌 queue requirement]
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by>1
    • base=main
    • label=A:automerge
    • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success = tests (00)
      • check-neutral = tests (00)
      • check-skipped = tests (00)
    • any of: [🛡 GitHub branch protection]
      • check-success = tests (01)
      • check-neutral = tests (01)
      • check-skipped = tests (01)
    • any of: [🛡 GitHub branch protection]
      • check-success = tests (03)
      • check-neutral = tests (03)
      • check-skipped = tests (03)
    • any of: [🛡 GitHub branch protection]
      • check-success = test-integration
      • check-neutral = test-integration
      • check-skipped = test-integration
    • any of: [🛡 GitHub branch protection]
      • check-success = golangci-lint
      • check-neutral = golangci-lint
      • check-skipped = golangci-lint
    • any of: [🛡 GitHub branch protection]
      • check-success = build (amd64)
      • check-neutral = build (amd64)
      • check-skipped = build (amd64)
    • any of: [🛡 GitHub branch protection]
      • check-success = build (arm64)
      • check-neutral = build (arm64)
      • check-skipped = build (arm64)
    • any of: [🛡 GitHub branch protection]
      • check-success = test-system
      • check-neutral = test-system
      • check-skipped = test-system
    • any of: [🛡 GitHub branch protection]
      • check-success = test-system-v2
      • check-neutral = test-system-v2
      • check-skipped = test-system-v2
• -conflict [📌 queue requirement]
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

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