Rule: self-assign PRs (assign)

• #assignee=0
• -closed
• -merged

Rule: forward-port patches to main branch (backport)

• label=forwardport-main
• merged
• merged [📌 backport requirement]

Rule: ask to resolve conflict (comment)

• conflict
• -author=github-actions[bot]
• -closed
• -merged

Rule: automatic squash and merge with success checks and the files matching the regex ^testing/environments/snapshot* are modified. (queue)

• #approved-reviews-by>=1
• -draft [📌 queue requirement]
• files~=^testing/environments/snapshot.*\.yml$
• label=automation
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
    • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
    • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success = CLA
      • check-neutral = CLA
      • check-skipped = CLA
    • any of: [🛡 GitHub branch protection]
      • check-success = buildkite/beats
      • check-neutral = buildkite/beats
      • check-skipped = buildkite/beats
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• check-success=buildkite/beats
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

✅ Rule: notify the backport policy (comment)

• -closed
• -label~=^backport
• -merged
• base=main

Rule: backport patches to 7.17 branch (backport)

• label~=^(backport-v7.17.0|backport-7.17)$
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.3 branch (backport)

• label=backport-v8.3.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.4 branch (backport)

• label=backport-v8.4.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.5 branch (backport)

• label=backport-v8.5.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.6 branch (backport)

• label=backport-v8.6.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.7 branch (backport)

• label=backport-v8.7.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.8 branch (backport)

• label=backport-v8.8.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.9 branch (backport)

• label=backport-v8.9.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.10 branch (backport)

• label=backport-v8.10.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.11 branch (backport)

• label=backport-v8.11.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.12 branch (backport)

• label=backport-v8.12.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.13 branch (backport)

• label=backport-v8.13.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.14 branch (backport)

• label=backport-v8.14.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.15 branch (backport)

• label~=^(backport-v8.15.0|backport-8.15)$
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.16 branch (backport)

• label~=^(backport-v8.16.0|backport-8.16)$
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.17 branch (backport)

• label=backport-8.17
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.18 branch (backport)

• label=backport-8.18
• merged
• merged [📌 backport requirement]

Rule: backport patches to 8.19 branch (backport)

• label=backport-8.19
• merged
• merged [📌 backport requirement]

Rule: backport patches to 9.0 branch (backport)

• label=backport-9.0
• merged
• merged [📌 backport requirement]

Rule: backport patches to 9.1 branch (backport)

• label=backport-9.1
• merged
• merged [📌 backport requirement]

---

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!

---

10 not applicable rules

Rule: close automated pull requests with bump updates if any conflict (close)

• author=github-actions[bot]
• conflict
• label=automation
• -closed
• -merged

Rule: automatic approval for automated pull requests with bump updates (review)

• author=github-actions[bot]
• files~=^testing/environments/snapshot.*\.yml$
• label=automation
• check-success=buildkite/beats

Rule: delete upstream branch after merging changes on testing/environments/snapshot* or it's closed (delete_head_branch)

• closed [📌 delete_head_branch requirement]
• all of:
  • files~=^testing/environments/snapshot.*\.yml$
  • head~=^updatecli_
  • label=automation
• any of:
  • closed
  • merged

Rule: delete upstream branch after merging changes on .go-version or it's closed (delete_head_branch)

• closed [📌 delete_head_branch requirement]
• all of:
  • files~=^\.go-version$
  • head~=^updatecli_
  • label=automation
• any of:
  • closed
  • merged

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

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

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

• #approved-reviews-by>=1
• -draft [📌 queue requirement]
• author=elastic-vault-github-plugin-prod[bot]
• files~=^\.mergify\.yml$
• head~=^add-backport-next.*
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
    • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
    • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
    • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
    • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
    • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success = CLA
      • check-neutral = CLA
      • check-skipped = CLA
    • any of: [🛡 GitHub branch protection]
      • check-success = buildkite/beats
      • check-neutral = buildkite/beats
      • check-skipped = buildkite/beats
• -closed [📌 queue requirement]
• -conflict [📌 queue requirement]
• check-success=buildkite/beats
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success = Configuration changed

Rule: delete upstream branch for mergify backports (delete_head_branch)

• closed [📌 delete_head_branch requirement]
• all of:
  • head~=^mergify/bp/.*
• any of:
  • closed
  • merged

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

• closed [📌 delete_head_branch requirement]
• all of:
  • author=elastic-vault-github-plugin-prod[bot]
  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
• any of:
  • closed
  • merged

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

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

Rule: forwardport docs changes to main (backport)

• base~=^\d+\.
• files~=^docs/
• label=docs
• merged
• merged [📌 backport requirement]

Mergify commands and options

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