Rule: automerge backported PR's for maintained branches (merge)

• -closed [📌 merge requirement]
• base=v7
• label=automerge
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
• #commits-behind = 0 [🛡 GitHub branch protection]
• -conflict [📌 merge requirement]
• -draft [📌 merge requirement]
• branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed
• any of: [🛡 GitHub branch protection]
  • check-success = unit-tests
  • check-neutral = unit-tests
  • check-skipped = unit-tests
• any of: [🛡 GitHub branch protection]
  • check-success = test-conformance
  • check-neutral = test-conformance
  • check-skipped = test-conformance
• any of: [🛡 GitHub branch protection]
  • check-success = test-ibc-examples
  • check-neutral = test-ibc-examples
  • check-skipped = test-ibc-examples
• any of: [🛡 GitHub branch protection]
  • check-success = test-cosmos-examples
  • check-neutral = test-cosmos-examples
  • check-skipped = test-cosmos-examples
• any of: [🛡 GitHub branch protection]
  • check-success = golangci-lint
  • check-neutral = golangci-lint
  • check-skipped = golangci-lint
• any of: [🛡 GitHub branch protection]
  • check-success = clippy-lint
  • check-neutral = clippy-lint
  • check-skipped = clippy-lint

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