Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: increase disk space in the CI runners #506

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
+5 −0

Merge branch 'main' into feature/increase-disk-space

98c411c
Select commit
Loading
Failed to load commit list.
Draft

ci: increase disk space in the CI runners #506

Merge branch 'main' into feature/increase-disk-space
98c411c
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Feb 7, 2025 in 0s

10 potential rules

Rule: ask to resolve conflict (comment)

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

Rule: notify the backport policy (comment, label)

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

Rule: remove-backport label (label)

  • label~=backport-v
  • -closed
  • -merged

Rule: backport patches to 1.16 branch (backport)

  • label=backport-v1.16
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 1.17 branch (backport)

  • label=backport-v1.17
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 1.18 branch (backport)

  • label=backport-v1.18
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 1.19 branch (backport)

  • label=backport-v1.19
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 1.20 branch (backport)

  • label=backport-v1.20
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 1.21 branch (backport)

  • label=backport-v1.21
  • merged
  • merged [📌 backport requirement]

Rule: backport patches to 1.22 branch (backport)

  • label=backport-v1.22
  • 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!

4 not applicable rules

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

  • author=apmmachine
  • check-success=buildkite/golang-crossbuild
  • files~=^go/Makefile.common
  • label=automation

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

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

Rule: squash and merge updatecli PRs after CI passes with golang bump updates (queue)

  • -draft [📌 queue requirement]
  • files~=^go/Makefile.common
  • head~=^updatecli
  • 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]
      • any of: [🛡 GitHub branch protection]
        • check-neutral = buildkite/golang-crossbuild
        • check-skipped = buildkite/golang-crossbuild
        • check-success = buildkite/golang-crossbuild
      • #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]
      • any of: [🛡 GitHub branch protection]
        • check-success = CLA
        • check-neutral = CLA
        • check-skipped = CLA
  • -closed [📌 queue requirement]
  • -conflict
  • -conflict [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

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

  • author=mergify[bot]
  • schedule=Mon-Mon 06:00-10:00[Europe/Paris]
  • #check-success>0
  • -closed
  • -merged
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

View more details on Mergify