You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is very nice that finally having [ci skip] in a PR's current commit does not activate the CI for pull_request. Unfortunately, it also did not run other things in .github/workflows such as the PR labeler and some triage actions (e.g., welcome message) that are unrelated to the CI testing.
How do I tell Actions that some workflows should not respect this new [skip ci] rule you have implemented on your server side?
Thank you!
Reacted by Matthew McPherrin, Chun Ly and Ronnie Dutta
I second this. GitHub Actions is specifically marketed as a workflow runner, not just CI/CD. It doesn't make sense then that [ci skip] and such doesn't run any workflow anymore. Labelling PRs isn't CI nor CD, it's a workflow.
Skipping all workflows is a bug that is being addressed. It should only skip pull_request and push. If you want to have a labeler workflow that can't be skipped you can switch to using pull_request_target which will always be run.
I too was thrown off as previously I had ci skip as a check for specific python builds. Now that I have a separate workflow for documentation, I had hoped that ci skip would skip these python build actions but still allow run the docs workflow. I suppose I can change my if statement
Skipping all workflows is a bug that is being addressed. It should only skip pull_request and push. If you want to have a labeler workflow that can't be skipped you can switch to using pull_request_target which will always be run.
Activity
chrispat commentedon Feb 9, 2021
I am not sure we need a specific way to override the rule right now as long as the other events run as expected.
pllim commentedon Feb 9, 2021
@chrispat , can you please clarify your response? My point is that I would expect PR labeler (https://github.com/actions/labeler) to still work but it does not kick off now if a pull request is opened and that first commit has
[ci skip]in it.SanderKnape commentedon Feb 10, 2021
I second this. GitHub Actions is specifically marketed as a workflow runner, not just CI/CD. It doesn't make sense then that
[ci skip]and such doesn't run any workflow anymore. Labelling PRs isn't CI nor CD, it's a workflow.chrispat commentedon Feb 10, 2021
Skipping all workflows is a bug that is being addressed. It should only skip
pull_requestandpush. If you want to have a labeler workflow that can't be skipped you can switch to usingpull_request_targetwhich will always be run.pllim commentedon Feb 10, 2021
Thanks for the update! What about release workflow that trigger when you push a tag out; is that immune from this feature?
astrochun commentedon Mar 4, 2021
I too was thrown off as previously I had
ci skipas a check for specific python builds. Now that I have a separate workflow for documentation, I had hoped thatci skipwould skip these python build actions but still allow run the docs workflow. I suppose I can change myifstatementchrispat commentedon Mar 5, 2021
@pllim release events should not be affected.
pllim commentedon Mar 15, 2021
I see that it no longer skips
pull_request_target. So as far as I am concerned, this is fixed for me. Thanks!pllim commentedon Apr 1, 2021
Looks like it is skipping everything again...
pllim commentedon Apr 5, 2021
And today it works as intended. 🤷
chore: ignore 'skip ci' flag in PRs
salzig commentedon Mar 12, 2024
is that also true for push of tags?