programmatic commit actually triggers new (invalid) workflow

Open maxheld83 opened this issue 6 years ago • 2 comments

what's up with this?

the workflow is not invalid
because this is a commit via GITHUB_TOKEN it shouldn't even trigger a new workflow run to begin with.

see https://github.com/maxheld83/remotes/commit/44750d3bada74fde5b537dbfd66b8853d9e1f30f

Jul 01 '19 18:07 maxheld83

as per the docs, any kind of event triggered via GITHUB_TOKEN is not supposed to trigger a new workflow run (makes sense) https://developer.github.com/actions/managing-workflows/workflow-configuration-options/#workflow-limitations.

Jul 02 '19 13:07 maxheld83

In other settings, commits + pushes from inside an action have, appropriately, not caused new workflow runs: https://github.com/r-lib/withr/commit/13807d2b86f826bd7e9201a15c0b551f32502945

This seems like a weird bug.

I wrote support about this.

Jul 02 '19 13:07 maxheld83