ci: split debian 11 amd/arm #533
Merged
This check has been archived and is scheduled for deletion.
Learn more about checks retention
Mergify / Summary
succeeded
Mar 20, 2025 in 4s
1 rule matches and 12 potential rules
Rule: automatic approval for automated pull requests with golang bump updates (review)
-
files~=^go/Makefile.common -
label=automation -
check-success=buildkite/golang-crossbuild
Rule: ask to resolve conflict (comment)
-
-closed -
-merged -
conflict
Rule: close automated pull requests with bump updates if any conflict (close)
-
-closed -
-merged -
conflict -
label=automation
Rule: notify the backport policy (comment, label)
-
-closed -
-label~=^backport -
-merged -
base=main
Rule: remove-backport label (label)
-
-closed -
-merged -
label~=backport-v
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]
✅ Rule: backport patches to 1.23 branch (backport)
-
label=backport-v1.23 -
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!
2 not applicable rules
Rule: squash and merge updatecli PRs after CI passes with golang bump updates (queue)
-
-closed[📌 queue requirement] -
files~=^go/Makefile.common -
head~=^updatecli -
label=automation - any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default]-
branch-protection-review-decision = APPROVED[🛡 GitHub branch protection] -
#approved-reviews-by >= 1[🛡 GitHub branch protection] -
#approved-reviews-by >= 1[🛡 GitHub repository ruleset rule] -
#approved-reviews-by >= 1[🛡 GitHub repository ruleset rule] -
#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
-
- any of: [🛡 GitHub branch protection]
-
check-success = buildkite/golang-crossbuild -
check-neutral = buildkite/golang-crossbuild -
check-skipped = buildkite/golang-crossbuild
-
-
- all of: [📌 queue conditions of queue
-
-conflict -
-conflict[📌 queue requirement] -
-draft[📌 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)
-
-closed -
-merged -
author=mergify[bot] -
schedule=Mon-Mon 06:00-10:00[Europe/Paris] -
#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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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
Loading