[skip ci] in commit message and tags
So as I understood, when I push a commit with '[skip ci]' substring and then push a tag on that commit, the tag won't trigger the build. Is that the intended behavior? Is there any way to force a build on a tag after the commit was skipped?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ilya Finkelshte... on 25 Aug, 2017 09:16 AM
I think most straightforward way is to use REST API.
Please look at this PowerShell example.
Do you believe it would make sense to implement setting to "ignore commit filters for tags"? It is not very complex to implement, just not sure how common is this scenario...
2 Posted by bazzilic on 25 Aug, 2017 10:09 AM
Well, actually my intuition was that even if commit has [skip ci], the tag will still trigger the build. I think, it makes sense to have a whitelist to build no matter what. E.g.,
force_build:
- tag: /v\d+\.\d+\.\d+/
- commit: /\[build me\]/
so this will force-build any commit if it was tagged with 'v1.2.3' and even will build a commit with commit message '[skip ci] [build me]'
What do you think?
3 Posted by Fahmi Akbar Wil... on 24 Feb, 2018 12:25 AM
I agree with that
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:26 AM.