Rule: ask to resolve conflict (comment)

• -author=apmmachine
• -closed
• -merged
• conflict

Rule: automatic approval for mergify pull requests with changes in bump-rules (review)

• author=mergify[bot]
• files~=^\.mergify\.yml$
• head~=^add-backport-next.*
• check-success=fleet-ci/pr-merge
• label=automation

Rule: automatic squash and merge with success checks and the files matching the regex ^.mergify.yml is modified. (queue)

• files~=^\.mergify\.yml$
• head~=^add-backport-next.*
• #approved-reviews-by>=1
• -draft [:pushpin: queue requirement]
• -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
• check-success=fleet-ci/pr-merge
• label=automation
• any of: [:twisted_rightwards_arrows: queue conditions]
  • all of: [:pushpin: queue conditions of queue default]
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]

Rule: delete upstream branch with changes on ^.mergify.yml that has been merged or closed (delete_head_branch)

• all of:
  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
  • label=automation
• closed [:pushpin: delete_head_branch requirement]
• any of:
  • closed
  • merged

Rule: notify the backport has not been merged yet (comment)

• -closed
• -merged
• author=mergify[bot]
• schedule=Mon-Mon 06:00-10:00[Europe/Paris]
• #assignee>=1
• #check-success>0

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