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 [:pushpin: 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 [: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]
    • #approved-reviews-by>=1 [🛡 GitHub branch protection]
    • #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
    • any of: [🛡 GitHub branch protection]
      • check-success=Build
      • check-neutral=Build
      • check-skipped=Build
    • any of: [🛡 GitHub branch protection]
      • check-success=Unit Tests
      • check-neutral=Unit Tests
      • check-skipped=Unit Tests
    • any of: [🛡 GitHub branch protection]
      • check-success=golangci-lint
      • check-neutral=golangci-lint
      • check-skipped=golangci-lint
    • any of: [🛡 GitHub branch protection]
      • check-success=k8s_object_rules-tests
      • check-neutral=k8s_object_rules-tests
      • check-skipped=k8s_object_rules-tests
    • any of: [🛡 GitHub branch protection]
      • check-success=pre_merge_agent-tests
      • check-neutral=pre_merge_agent-tests
      • check-skipped=pre_merge_agent-tests
    • any of: [🛡 GitHub branch protection]
      • check-success=process_api_server_rules-tests
      • check-neutral=process_api_server_rules-tests
      • check-skipped=process_api_server_rules-tests
    • any of: [🛡 GitHub branch protection]
      • check-success=process_controller_manager_rules-tests
      • check-neutral=process_controller_manager_rules-tests
      • check-skipped=process_controller_manager_rules-tests
    • any of: [🛡 GitHub branch protection]
      • check-success=process_kubelet_rules-tests
      • check-neutral=process_kubelet_rules-tests
      • check-skipped=process_kubelet_rules-tests
    • any of: [🛡 GitHub branch protection]
      • check-success=process_scheduler_rules-tests
      • check-neutral=process_scheduler_rules-tests
      • check-skipped=process_scheduler_rules-tests

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

Rule: notify the backport policy (comment, label)

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

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