From b3f01f14506322a4a0984042e5957efc3e1e119c Mon Sep 17 00:00:00 2001 From: Pamphile Roy Date: Wed, 17 Aug 2022 19:59:33 +0200 Subject: DOC: update skip section and fix formatting. [skip ci] --- doc/source/dev/development_workflow.rst | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) (limited to 'doc/source/dev') diff --git a/doc/source/dev/development_workflow.rst b/doc/source/dev/development_workflow.rst index a7c915b42..b49a96d7a 100644 --- a/doc/source/dev/development_workflow.rst +++ b/doc/source/dev/development_workflow.rst @@ -197,17 +197,14 @@ platforms to building the docs. In some cases you already know that CI isn't needed (or not all of it), for example if you work on CI config files, text in the README, or other files that aren't involved in regular build, test or docs sequences. In such cases you may explicitly skip CI by including one of these -fragments in your commit message:: - - ``[ci skip]``: skip as much CI as possible (not all jobs can be skipped) - ``[skip github]``: skip GitHub Actions "build numpy and run tests" jobs - ``[skip travis]``: skip TravisCI jobs - ``[skip azurepipelines]``: skip Azure jobs - -*Note*: unfortunately not all CI systems implement this feature well, or at all. -CircleCI supports ``ci skip`` but has no command to skip only CircleCI. -Azure chooses to still run jobs with skip commands on PRs, the jobs only get -skipped on merging to master. +fragments in your commit message: + +* ``[skip ci]``: skip all CI +* ``[skip github]``: skip GitHub Actions "build numpy and run tests" jobs +* ``[skip actions]``: skip all GitHub Actions +* ``[skip travis]``: skip TravisCI jobs +* ``[skip azp]``: skip Azure jobs +* ``[skip circle]``: skip CircleCI jobs Test building wheels ~~~~~~~~~~~~~~~~~~~~ -- cgit v1.2.1