ci: delay checking ci/skip/multi-arch-build label#5971
Merged
mergify[bot] merged 1 commit intoceph:develfrom Jan 28, 2026
Merged
ci: delay checking ci/skip/multi-arch-build label#5971mergify[bot] merged 1 commit intoceph:develfrom
mergify[bot] merged 1 commit intoceph:develfrom
Conversation
nixpanic
force-pushed
the
testing/multi-arch-check
branch
6 times, most recently
from
56a9064 to
7d7b337
Compare
nixpanic
added
the
ci/skip/multi-arch-build
nixpanic
force-pushed
the
testing/multi-arch-check
branch
5 times, most recently
from
ab06a71 to
0fef12f
Compare
nixpanic
added
ci/skip/e2e
Member
Author
|
Tested a lot, and this seems to work now. See the attempts of the last runs at https://github.com/ceph/ceph-csi/actions/runs/21289467990/job/61279172064?pr=5971 |
nixpanic
force-pushed
the
testing/multi-arch-check
branch
from
0fef12f to
3454814
Compare
nixpanic
force-pushed
the
testing/multi-arch-check
branch
3 times, most recently
from
0e2f093 to
3d64781
Compare
When a GitHub Event is created, the labels of the PR are set to the current values. Mergify will only set the labels, or copy the labels to the PR once the PR is created. That means the initial GitHub Event does not have the right labels set yet. In order to really skip the multi-arch-build, and run single-arch-build instead, the label needs to be checked from the PR, instead of compared from the labels in the GitHub Event. Signed-off-by: Niels de Vos <[email protected]>
nixpanic
force-pushed
the
testing/multi-arch-check
branch
from
3d64781 to
96ca63f
Compare
nixpanic
added
ci/skip/multi-arch-build
Rakshith-R
approved these changes
Jan 28, 2026
78 tasks
Contributor
Merge Queue Status✅ The pull request has been merged at 96ca63f This pull request spent 5 minutes 29 seconds in the queue, including 5 minutes 17 seconds running CI. Required conditions to merge
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a GitHub Event is created, the labels of the PR are set to the
current values. Mergify will only set the labels, or copy the labels to
the PR once the PR is created. That means the initial GitHub Event does
not have the right labels set yet.
In order to really skip the multi-arch-build, and run single-arch-build
instead, the label needs to be checked from the PR, instead of compared
from the labels in the GitHub Event.