tag:help.appveyor.com,2012-11-13:/discussions/problems/543-skip-ci-not-workingAppVeyor: Discussion 2018-08-25T02:21:05Ztag:help.appveyor.com,2012-11-13:Comment/337880482014-07-15T19:36:18Z2014-07-15T19:36:18Z[skip ci] not working<div><p>I've noticed that builds with <code>[skip ci]</code> in the
comment message still trigger an appveyor run: <a href=
"https://ci.appveyor.com/project/Mapbox/node-sqlite3-163/build/1.0.43">
https://ci.appveyor.com/project/Mapbox/node-sqlite3-163/build/1.0.43</a>.
This seems to conflict with the docs: <a href=
"http://www.appveyor.com/docs/how-to/skip-build">http://www.appveyor.com/docs/how-to/skip-build</a>.</p>
<p>Also, it would be great to support another term to be able to
skip that is different than travis. I often want to skip travis
builds but not appveyor builds and vice versa. What about
<code>[skip appveyor]</code>?</p></div>danetag:help.appveyor.com,2012-11-13:Comment/337880482014-07-15T20:34:10Z2014-07-15T20:34:10Z[skip ci] not working<div><p>Will take a look. <code>[skip appveyor]</code> is nice idea,
thanks.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/337880482014-07-16T06:00:25Z2014-07-16T06:00:25Z[skip ci] not working<div><p>Trying to reproduce by pushing changes with [skip ci] in
comments... How did you run that build - using "New build"
button?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/337880482014-07-16T06:38:22Z2014-07-16T06:38:22Z[skip ci] not working<div><p>No. It was a single commit if I recall correctly.</p></div>danetag:help.appveyor.com,2012-11-13:Comment/337880482014-07-16T06:41:05Z2014-07-16T06:41:05Z[skip ci] not working<div><p>Hm, that's strange... Could you try reproducing it again?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/337880482014-07-16T16:37:09Z2014-07-16T16:37:09Z[skip ci] not working<div><p>I can not replicate using the same commit message as before. So
perhaps this was just a one time hiccup?</p></div>danetag:help.appveyor.com,2012-11-13:Comment/337880482014-07-16T16:47:38Z2014-07-16T16:47:38Z[skip ci] not working<div><p>Anyway, I've checked-in <code>[skip appveyor]</code> support -
will deploy tomorrow.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/337880482014-07-17T08:39:59Z2014-07-17T08:39:59Z[skip ci] not working<div><p>Update with <code>[skip appveyor]</code> has been deployed.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/337880482017-10-28T05:21:23Z2017-10-28T05:21:23Z[skip ci] not working<div><p>[skip ci] still doesn't work for AppVeyor.</p>
<p>In this instance, I was doing just documentation updates and wanted to skip both Travis and AppVeyor.</p>
<p><a href="https://ci.appveyor.com/project/acgetchell/causal-sets-explorer/build/1.0.70">https://ci.appveyor.com/project/acgetchell/causal-sets-explorer/bui...</a></p></div>acgetchelltag:help.appveyor.com,2012-11-13:Comment/337880482017-10-29T19:52:40Z2017-10-29T19:52:40Z[skip ci] not working<div><p><strong>@acgetchell</strong> we recently changed behavior to look for <code>[skip ci]</code> (and other skip strings in commit messages) only in the text before first empty line. We did that because a lot of confusion happens then people merge and squash multiple commits and single older commit prevents whole merge commit to be built. You can move <code>[skip ci]</code> to the first line, or make it in the second line, but without empty line before it, or you can skip commit with <code>.md</code> files changed as described <a href="https://www.appveyor.com/docs/how-to/filtering-commits/#skip-commits-2">here</a></p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/337880482017-11-04T20:08:12Z2017-11-04T20:08:13Z[skip ci] not working<div><p>It's not clear to me why this commit would have ran on AppVeyor, even given your new criteria:</p>
<p><a href="https://ci.appveyor.com/project/meteor/meteor/build/83/job/lvsqxs0n57j8oy82">https://ci.appveyor.com/project/meteor/meteor/build/83/job/lvsqxs0n...</a></p></div>Jesse Rosenbergertag:help.appveyor.com,2012-11-13:Comment/337880482017-11-04T20:11:25Z2017-11-04T20:11:27Z[skip ci] not working<div><p>Also, it seems <a href="https://www.appveyor.com/docs/how-to/filtering-commits/#skip-directive-in-commit-message">the documentation</a> linked to above may need to be updated if the commit message skip directives are (now) only observed under particular circumstances, since it still dictates "anywhere to commit message".</p></div>Jesse Rosenbergertag:help.appveyor.com,2012-11-13:Comment/337880482017-11-04T21:12:10Z2017-11-04T21:12:59Z[skip ci] not working<div><p>Yes, it still ignores [skip ci] when it's the first line of the commit message.</p>
<p><a href="https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.207">https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.207</a></p></div>acgetchelltag:help.appveyor.com,2012-11-13:Comment/337880482017-11-09T03:11:29Z2017-11-09T03:11:29Z[skip ci] not working<div><p>Documentation is updated. Commits referenced both <a href="https://ci.appveyor.com/project/meteor/meteor/build/83/job/lvsqxs0n57j8oy82">here</a> and <a href="https://ci.appveyor.com/project/acgetchell/cdt-plusplus/build/1.0.207">here</a> do not <strong>not</strong> have <code>[skip ci]</code> in the first line of commit message. They both are after first empty line. You can open GitHub webhook content and see it yourself: part with <code>[skip ci]</code> will be after <code>\n\n</code>. Probably <code>[skip ci]</code> was added into <strong>description</strong> part in GitHub (or GitHub for desktop) UI, which is separated with empty line behind the scenes.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/337880482017-11-09T12:04:12Z2017-11-09T12:04:12Z[skip ci] not working<div><p>I wrote that commit message with <code>vi</code> and used the same format that I believe is the standard usage case:</p>
<pre>
<code>Commit Subject
Commit Body/Description</code>
</pre>
<p>This would be the equivalent of <code>Commit Subject\n\nCommit Description</code>.</p>
<p>The default commit message format produced by <code>git</code> is in that same format when doing squashes, merge commits, etc., so I don't see how the format that I'm using is wrong. It's also the "best practice" format which is recommended by most editors, and as you pointed out, the way that GitHub expects it to be.</p>
<p>Are you asking developers to use a different format? Like this:</p>
<pre>
<code>Commit Subject
[skip ci]
Commit Body/Description</code>
</pre>
<p>If not, can you give an example of a <code>[skip ci]</code> commit message, which follows standard best practices, which would actually skip the CI?</p></div>Jesse Rosenbergertag:help.appveyor.com,2012-11-13:Comment/337880482017-11-09T18:05:53Z2017-11-09T18:05:53Z[skip ci] not working<div><p>Jesse, thank you for clarifying. I would say like this for example:</p>
<pre>
<code>Commit Subject
Update user documentation [skip ci]
Commit Body/Description
Explained how to do something</code>
</pre>
<p>Sorry for the trouble. We tried to eliminate one confusion but it seems that brought another.</p></div>Ilya Finkelshteyn