Respect [skip ci]

[IanButterworth]

We should probably stick to the standard github approach.

https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs

Workflows that would otherwise be triggered using on: push or on: pull_request won't be triggered if you add any of the following strings to the commit message in a push, or the HEAD commit of a pull request:

• [skip ci]
• [ci skip]
• [no ci]
  ...

[inkydragon]

commit message in a push, or the HEAD commit of a pull request

And maybe: ... OR title of the pull request OR label of a pull request.

In both cases, when one removes the "skip ci" in the title or removes the label, new commits will trigger the CI normally.

[DilumAluthge]

Buildkite is supposed to already come with [skip ci] support built in: https://buildkite.com/docs/pipelines/skipping#ignore-a-commit

If I recall correctly, Buildkite will not respect [skip ci] when a PR is first opened (that is, Buildkite will always run CI when a PR is first opened), but if you push subsequent commits to an existing PR, Buildkite will respect [skip ci] if present in those commit messages.

I'm not sure if that is a bug or the intended behavior.

[IanButterworth]

Interesting. It might be nice if it could check the PR title too, which seems possible from your link

Also some granularity

• [skip ci] skips all CI
• [skip tests] builds but skips tests