Rule: Automatic merge on approval release (merge)

• -closed [📌 merge requirement]
• base=release
• #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]
• approved-reviews-by>=1
• any of: [📌 merge -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed
• any of: [🛡 GitHub branch protection]
  • check-success=DCO
  • check-neutral=DCO
  • check-skipped=DCO
• any of: [🛡 GitHub branch protection]
  • check-success=WIP
  • check-neutral=WIP
  • check-skipped=WIP
• any of: [🛡 GitHub branch protection]
  • check-success=Max TF pre-commit
  • check-neutral=Max TF pre-commit
  • check-skipped=Max TF pre-commit
• any of: [🛡 GitHub branch protection]
  • check-success=Min TF pre-commit (.)
  • check-neutral=Min TF pre-commit (.)
  • check-skipped=Min TF pre-commit (.)
• any of: [🛡 GitHub branch protection]
  • check-success=Validate PR title
  • check-neutral=Validate PR title
  • check-skipped=Validate PR title
• any of: [🛡 GitHub branch protection]
  • check-success=renovate:config
  • check-neutral=renovate:config
  • check-skipped=renovate:config

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