Add should-skip-ci step in ci.yaml
#2478
Merged
+34
−6
Conversation
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
VeckoTheGecko
force-pushed
the
smarter-ci
branch
from
312c7d4 to
0ae3d03
Compare
VeckoTheGecko
force-pushed
the
smarter-ci
branch
2 times, most recently
from
e442a08 to
648f92f
Compare
VeckoTheGecko
force-pushed
the
smarter-ci
branch
from
648f92f to
a2bc3c1
Compare
VeckoTheGecko
force-pushed
the
smarter-ci
branch
from
a2bc3c1 to
f3aca4c
Compare
Contributor
Author
|
i think this is good to go @erikvansebille . I was experiencing some weirdness but I'm not really sure if that's due to bugginess or due to improper testing on my behalf, so we might need to revert/iterate down the line if this isn't behaving as expected |
erikvansebille
approved these changes
Jan 19, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Ok, so looks like there is no option for us to apply the label from the get go (unlike issue templates, PR templates don't support this). So we need to resort to doing it manually. I've also added a check here that we're only running CI on the main repo (not forks).
Doing some manual testing here, then we can merge.
Fixes #2475