Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Buildkite introduction: repo registration #326

Merged
merged 1 commit into from
Aug 7, 2023

repo registration

cd519bd
Select commit
Loading
Failed to load commit list.
Merged

Buildkite introduction: repo registration #326

repo registration
cd519bd
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 7, 2023 in 1s

8 potential rules

⚠️ The pull request has been merged by @alexsapran

Rule: self-assign PRs (assign)

  • #assignee=0
  • -closed
  • -merged

Rule: ask to resolve conflict (comment)

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

Rule: notify the backport policy (comment)

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

Rule: backport patches to 8.5 branch (backport)

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

Rule: backport patches to 8.6 branch (backport)

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

Rule: backport patches to 8.7 branch (backport)

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

Rule: backport patches to 8.8 branch (backport)

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

Rule: backport patches to 8.9 branch (backport)

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

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

🚀  You can help us by becoming a sponsor!


5 not applicable rules

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

  • all of:
    • files~=^\.go-version$
    • head~=^updatecli
    • 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]
  • files~=^\.mergify\.yml$
  • head~=^add-backport-next.*
  • label=automation
  • check-success=fleet-ci/pr-merge

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.*
  • label=automation
  • #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
  • 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
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