Rule: squash and merge updatecli PRs after CI passes (queue)

• head~=^updatecli
• label=automation
• -conflict
• -draft [:pushpin: queue requirement]
• -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
• any of: [:twisted_rightwards_arrows: queue conditions]
  • all of: [:pushpin: queue conditions of queue default]
    • any of: [🛡 GitHub branch protection]
      • check-success=CI-approved contributor
      • check-neutral=CI-approved contributor
      • check-skipped=CI-approved contributor
    • any of: [🛡 GitHub branch protection]
      • check-success=CLA
      • check-neutral=CLA
      • check-skipped=CLA
    • any of: [🛡 GitHub branch protection]
      • check-success=apm-ci/pr-merge
      • check-neutral=apm-ci/pr-merge
      • check-skipped=apm-ci/pr-merge
    • any of: [🛡 GitHub branch protection]
      • check-success=elasticsearch-ci/docs
      • check-neutral=elasticsearch-ci/docs
      • check-skipped=elasticsearch-ci/docs
    • any of: [🛡 GitHub branch protection]
      • check-success=system-test
      • check-neutral=system-test
      • check-skipped=system-test
    • any of: [🛡 GitHub branch protection]
      • check-success=lint
      • check-neutral=lint
      • check-skipped=lint

Rule: delete updatecli branch after merging/closing it (delete_head_branch)

• all of:
  • head~=^updatecli
  • 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]
• #check-success>0

Rule: squash and merge backport PRs after CI passes (queue)

• author=mergify[bot]
• label=backport
• -conflict
• -draft [:pushpin: queue requirement]
• -mergify-configuration-changed [:pushpin: queue -> allow_merging_configuration_change setting requirement]
• any of: [:twisted_rightwards_arrows: queue conditions]
  • all of: [:pushpin: queue conditions of queue default]
    • any of: [🛡 GitHub branch protection]
      • check-success=CI-approved contributor
      • check-neutral=CI-approved contributor
      • check-skipped=CI-approved contributor
    • any of: [🛡 GitHub branch protection]
      • check-success=CLA
      • check-neutral=CLA
      • check-skipped=CLA
    • any of: [🛡 GitHub branch protection]
      • check-success=apm-ci/pr-merge
      • check-neutral=apm-ci/pr-merge
      • check-skipped=apm-ci/pr-merge
    • any of: [🛡 GitHub branch protection]
      • check-success=elasticsearch-ci/docs
      • check-neutral=elasticsearch-ci/docs
      • check-skipped=elasticsearch-ci/docs
    • any of: [🛡 GitHub branch protection]
      • check-success=system-test
      • check-neutral=system-test
      • check-skipped=system-test
    • any of: [🛡 GitHub branch protection]
      • check-success=lint
      • check-neutral=lint
      • check-skipped=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