Hi Mike, TIL, both are in fact accepted: https://docs.travis-ci.com/user/customizing-the-build#skipping-a-build
Luca Il giorno lun 10 feb 2020 alle ore 17:32 Mike Rumph <[email protected]> ha scritto: > > This thread mentions [skip ci] but the Travis issue mentions [ci skip] and > [ci-skip]. > Are all of these forms recognized? > > On Mon, Feb 10, 2020 at 4:23 AM Eric Covener <[email protected]> wrote: >> >> On Mon, Feb 10, 2020 at 1:44 AM Ruediger Pluem <[email protected]> wrote: >> > >> > >> > >> > On 02/08/2020 12:01 PM, Luca Toscano wrote: >> > > Hi everybody, >> > > >> > > Travis is able to read commit messages and skip the CI workflow if the >> > > "[skip ci]" magic sequence is added somewhere. I keep forgetting about >> > > it too, but it would be nice if we could start using it to avoid using >> > > CI resources/workers when not needed (like docs changes, entries in >> > > STATUS, etc..). I didn't find a way to instruct Travis to avoid >> > > triggering a build if only certain file types are committed, so the >> > > only solution for the moment is to manually add the aforementioned >> > > sequence :( >> > > >> > > It is not a big deal to trigger builds even for docs etc.., but the >> > > ASF resources/workers are limited (and shared among projects IIUC) so >> > > I am only suggesting to be good neighbors :) If this is totally insane >> > > or unacceptable I'll back off and stop vouching for it I promise! >> > > >> > >> > Thanks for pointing this out, but I forget this as well in many cases :-). >> > The only one here who seems to remember this always is IMHO Joe. Maybe >> > he has some tips how we can get better here. >> > >> > Regards >> > >> > Rüdiger >> >> Is there anything possible in SVN like a pre-commit hook that can see >> what changed and append [skip ci] unless some other incantantation is >> present? >> >> >> -- >> Eric Covener >> [email protected]
