Github allows to do this right away

[smnbbrv]

Hi

thanks for your work!

However the current version of github actions allows you to do this in a more elegant way:

jobs:
  main:
    name: Build and test
    runs-on: ubuntu-latest
    if: "!contains(github.event.head_commit.message, '[ci skip]')"

Probably worth mentioning it in the readme...

[veggiemonk]

This is awesome! Thank you @smnbbrv

[ain]

Cool idea, although it comes across as a failure (and throws failure email):

[smnbbrv]

Does not for me... See https://github.com/ngx-grpc/protoc-gen-ng/commits/master

[MGatner]

I'm baffled how @smnbbrv got this to work without failures. Every time I use ci skip it instantly generates a failure and corresponding email.

EDIT: Actually it appears this is a bug with an active ticket: https://github.community/t5/GitHub-Actions/Status-of-workflows-with-no-running-jobs/td-p/37160

[ain]

@MGatner of course the discussion there has no binding to this particular repo.

It clearly fails and I can't imagine the circumstances of how this could succeed. The discussion you linked to proves this assumption true.

[MGatner]

If I understand correctly the report and subsequent response, workflows that run now jobs should count as "skipped", but currently count incorrectly as failures. I'm hopeful that when this issue is resolved this method of providing ci skip functionality will be viable and work consistent with other pipelines.

[smnbbrv]

Could you post some failure examples? For me it works like a charm again and again

[MGatner]

Unfortunately all mine are on private repos right now, but they are definitely happening. Here's the relevant portion of my workflow:

name: PHP Unit Tests
on:
  push:
    branches: 
      - develop
jobs:
  main:
    name: Build and test
    strategy:
      matrix:
        php-versions: ['7.2', '7.3', '7.4']
    runs-on: ubuntu-latest
    if: "!contains(github.event.head_commit.message, '[ci skip]')"

The commit with matching text:

The failed action reference:

The failed email response:

Notice that the commits correctly lack a check or X, even though Actions records the failures.

[smnbbrv]

What’s really different to my builds here is matrix. My reasons for ci skip are coming from a semantic release CHANGELOG.md commit - I don’t want it to trigger another release = avoid infinite loop. Maybe the matrix build is the key to the problem here...

[fennecdjay]

Looks like it works for me.
if have

runs-on: either linux osx or windows
if: "!contains(github.event.head_commit.message, '[skip ci]')"

logs