Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[skip ci] skips also non-CI workflows
See original GitHub issueHello! This is a direct follow up of #774 and https://github.blog/changelog/2021-02-08-github-actions-skip-pull-request-and-push-workflows-with-skip-ci/ .
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!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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.I see that it no longer skips
pull_request_target. So as far as I am concerned, this is fixed for me. Thanks!