I noticed also that there is no way to skip Azure runs, let me know if you want me to port over the 30 or so lines that allow using[skip azp] in a commit title:

https://github.com/mne-tools/mne-python/blob/f3a7dece8d4361265e055f617e98c197c7cba07e/azure-pipelines.yml#L16-L36

Or the SciPy variant that allows having that same thing anywhere in the commit message:

https://github.com/scipy/scipy/blob/5b3a3b440525aa5038e2cead1f9b4f23a610cd9f/azure-pipelines.yml#L35-L54

(Both were developed originally for MNE by@GuillaumeFavelier !)

Couldn't resist the temptation to put[skip azp] in there (EDIT: the SciPy variant where[skip azp] can be anywhere in the commit message), seems to be working:

https://dev.azure.com/matplotlib/matplotlib/_build/results?buildId=20049&view=results

I'll push a commit without it in there just to make sure I didn't break the main tests, though...

Merge step appears to be working:

https://app.circleci.com/pipelines/github/matplotlib/matplotlib/10532/workflows/b8386bc4-3792-4c40-afae-e5b7edf8b973/jobs/62393/parallel-runs/0/steps/0-102

Ready for review/merge from my end

OK, but maybe the skip command needs to be documented in the dev docs somewhere? Though I'm not sure under what conditions we'd skip Azure versus the other tests...

Though I'm not sure under what conditions we'd skip Azure versus the other tests...

For just one example, if you just want to update some documentation wording and make sure you didn't do something bad RST/Sphinx-wise, something like[ci skip] is inappropriate because CircleCI won't run, and it's wasteful to run the Azure and GH-Actions tests just for a tiny doc update.

For another example, maintainers doing CI maintenance like in this PR where just.circleci/config.yml is changed but you want to make sure things still work, same story about Azure and GH-Actions.

I have found having this level of individual control over each CI provider to be pretty useful over the years of maintaining repos.

Maybe I misunderstood, does this also skip all the GitHub action tests somehow?

OK, but maybe the skip command needs to be documented in the dev docs somewhere?

Maybe I misunderstood, does this also skip all the GitHub action tests somehow?

No,[skip actions] does this, and is built into / dealt with by GH-Actionsautomagically, just like[skip appveyor] is built intoAppVeyor, and[skip travis] is built intoTravis. On the other hand,CircleCI andAzure do not support these out of the box, so the code added here adds support for them.

I just pushed a doc update that hopefully makes it clearer

[skip circle] works now:

https://app.circleci.com/pipelines/github/matplotlib/matplotlib/10539/workflows/dfc52fcc-fef4-4279-93c1-7b930bed224f/jobs/62400

Will push a commit to skip everything except Circle so that we can see that the doc-only change to the devdocs I made doesn't break anything...

Now you need to commit without skipping Circle though, to see the merging worked.

Now you need to commit without skipping Circle though, to see the merging worked.

You can look at any of the commits that preceded that one above, e.g.https://app.circleci.com/pipelines/github/matplotlib/matplotlib/10541/workflows/1a5c01bb-2de1-4053-90a8-ebdd6898c06c/jobs/62402/parallel-runs/0/steps/0-103. But I'll push another one without any skips once we settle on if the file-based method is good enough or if I need to dig into bash more...

Merge worked, and it's building:

https://app.circleci.com/pipelines/github/matplotlib/matplotlib/10573/workflows/a164cea0-930c-4151-a0a8-eeccaf67c1ec/jobs/62444/parallel-runs/0/steps/0-103

Will now push another commit with[skip circle] just to make sure I didn't break that

[skip circle] workedhttps://app.circleci.com/pipelines/github/matplotlib/matplotlib/10574/workflows/d5cedeb0-adbb-493f-94fc-02c482e8f8db/jobs/62445/parallel-runs/0/steps/0-102

FYI@QuLogic I fixed up the shell scripting to avoid using files in the process.