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

• base=main
• #approved-reviews-by>1
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by>=2 [🛡 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=pre-test
      • check-neutral=pre-test
      • check-skipped=pre-test
    • any of: [🛡 GitHub branch protection]
      • check-success=test (macos-latest)
      • check-neutral=test (macos-latest)
      • check-skipped=test (macos-latest)
    • any of: [🛡 GitHub branch protection]
      • check-success=test (ubuntu-latest)
      • check-neutral=test (ubuntu-latest)
      • check-skipped=test (ubuntu-latest)
    • any of: [🛡 GitHub branch protection]
      • check-success=status
      • check-neutral=status
      • check-skipped=status

Rule: backport patches to v28.x.y branch (backport)

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

Rule: backport patches to v29.x.y branch (backport)

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

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