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

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

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

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

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

• author=mergify[bot]
• check-success=Cloudbeat-CI / Build (pull_request)
• check-success=Cloudbeat-CI / Integration Tests (pull_request)
• check-success=UnitTests / Unit Tests (pull_request)
• files~=^\.mergify\.yml$
• head~=^add-backport-next.*
• label=automation

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

• check-success=Cloudbeat-CI / Build (pull_request)
• check-success=Cloudbeat-CI / Integration Tests (pull_request)
• check-success=UnitTests / Unit Tests (pull_request)
• files~=^\.mergify\.yml$
• head~=^add-backport-next.*
• label=automation
• #approved-reviews-by>=1
• -draft [📌 queue requirement]
• any of: [📌 queue -> configuration change requirements]
  • -mergify-configuration-changed
  • check-success=Configuration changed
• any of: [🔀 queue conditions]
  • all of: [📌 queue conditions of queue default]
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
    • branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success=CLA
      • check-neutral=CLA
      • check-skipped=CLA
    • any of: [🛡 GitHub branch protection]
      • check-success=Package Cloudbeat (docker)
      • check-neutral=Package Cloudbeat (docker)
      • check-skipped=Package Cloudbeat (docker)
    • any of: [🛡 GitHub branch protection]
      • check-success=Package Cloudbeat (tar.gz)
      • check-neutral=Package Cloudbeat (tar.gz)
      • check-skipped=Package Cloudbeat (tar.gz)
    • any of: [🛡 GitHub branch protection]
      • check-success=Manifest Tests
      • check-neutral=Manifest Tests
      • check-skipped=Manifest Tests
    • any of: [🛡 GitHub branch protection]
      • check-success=Test Rego Policies
      • check-neutral=Test Rego Policies
      • check-skipped=Test Rego Policies
    • any of: [🛡 GitHub branch protection]
      • check-success=Build docker images
      • check-neutral=Build docker images
      • check-skipped=Build docker images
    • any of: [🛡 GitHub branch protection]
      • check-success=Lint
      • check-neutral=Lint
      • check-skipped=Lint
    • any of: [🛡 GitHub branch protection]
      • check-success=Unit Test
      • check-neutral=Unit Test
      • check-skipped=Unit Test
    • any of: [🛡 GitHub branch protection]
      • check-success=CNVM CI
      • check-neutral=CNVM CI
      • check-skipped=CNVM CI
    • any of: [🛡 GitHub branch protection]
      • check-success=CIS Azure CI
      • check-neutral=CIS Azure CI
      • check-skipped=CIS Azure CI
    • any of: [🛡 GitHub branch protection]
      • check-success=CIS AWS CI
      • check-neutral=CIS AWS CI
      • check-skipped=CIS AWS CI
    • any of: [🛡 GitHub branch protection]
      • check-success=CIS GCP CI
      • check-neutral=CIS GCP CI
      • check-skipped=CIS GCP CI

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 [📌 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