[ci skip] is ignored on commits that are pushed with 'git push --tags <remote> <branch>'
It looks like GitHub delivers two almost identical payloads
(except for a before-ref of all zeroes for the tag commits as seen
here)
and even though the string [ci skip] is present in
both of them, only one is ignored and the second one (probably the
tag event payload) triggers a build.
Please see the second and forth builds in this screenshot:
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
Support Staff 1 Posted by Feodor Fitsner on 13 Mar, 2014 01:30 PM
Oh, I will take a look. Good case, thanks!
- Feodor
Support Staff 2 Posted by Feodor Fitsner on 13 Mar, 2014 11:38 PM
It's been fixed and update deployed. Now, pushing tags won't trigger a new build.
3 Posted by Hari Menon on 13 Mar, 2014 11:54 PM
That's fantastic! Thanks for a very quick fix and push.
I can confirm that it is some awesome continuous deployment experience now... :)
Thanks once again for AppVeyor!
Support Staff 4 Posted by Feodor Fitsner on 13 Mar, 2014 11:55 PM
Looks nice :)
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:38 AM.