jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

support skip ci in azure pipelines, and support it properly in github actions pipelines (#17561)

Browse source 
* support skip ci in azure pipelines

* [skip ci] example of a commit that skips CI

* example of a commit that does not skip CI

* fix github actions logic for ci skip handling

* [skip ci] example of a commit that skips CI for all pipelines

* example of a commit that does not skip CI for any pipeline
This commit is contained in:
Timothee Cour 2021-04-20 00:01:53 -07:00 • committed by GitHub
commit fb02b56957
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 45 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/contributing.rst
View file

@ -508,9 +508,10 @@ Continuous Integration (CI)
1. Continuous Integration is by default run on every push in a PR; this clogs
the CI pipeline and affects other PR's; if you don't need it (e.g. for WIP or
documentation only changes), add `[ci skip]` to your commit message title.
This convention is supported by `Appveyor
<https://www.appveyor.com/docs/how-to/filtering-commits/#skip-directive-in-commit-message>`_
documentation only changes), add `[skip ci]` to your commit message title.
This convention is supported by our github actions pipelines and our azure pipeline
as well as our former other pipelines:
`Appveyor <https://www.appveyor.com/docs/how-to/filtering-commits/#skip-directive-in-commit-message>`_
and `Travis <https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build>`_.
2. Consider enabling CI (azure, GitHub actions and builds.sr.ht) in your own Nim fork, and