Is there a way to ignore "[skip ci]" for tag pushes?

[laur89]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

I'm using zest releaser for releasing python projects. To do so, its executable is ran from an action itself, which causes couple of version change commits, and a tag.

The tool adds [skip ci] (configurable) message to the commits, as version bumps should not trigger ci/cd runs.
But as a result, the pushed tag also fails to start a workflow.

How to make sure a tag push event, which is generated by a workflow, still triggers another workflow execution?

---

And to be clear, I have confirmed it is in fact the commit message that's causing the tag push to be ignored. Changing message to [CI SKIP] (or any other string for that matter) doesn't work with github, and a resulting tag push was processed by the pipeline.

[laur89]

Thanks, changing workflow trigger from just push to on: [push, create] did the trick.

As a side question, is it expected that workflow runs triggered by said tag pushes/creations don't show any causing entity label on the Actions page, like it does for push event? Note the missing value whereas for workflow runs triggered by pushes onto master have master label and an earlier tag push (without a [skip ci] message) also shows a tag label: