Check run result is pushed to any workflow, rather than the executing workflow #4
Labels
Comments
jwgmeligmeyling
added
bug
This was referenced Jun 17, 2020
|
I'm seeing a similar problem with one of my actions, however I have multiple workflow files and the check run is not always associated the correct workflow (usually the first one in the list - since push events happen before pull_requests it tends to be a push event). So I'm watching this and your discourse discussion with interest. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Github Actions run within a Workflow Run. Each Workflow Run is associated with its own Check Suite. Whenever we post a Check Run, a Check Suite is created unless a Check Suite for that application already exists. However, when multiple workflows are triggered for an event (or multiple events trigger multiple runs of the same workflow) , multiple possible Workflow Runs and thus multiple Check Suites will be available. Unfortunately, there is no way for us to pick a Check Suite when creating a new Check Run. This is a limitation in the Github Checks API. As a result, currently results generated during workflows on a
pull_requestevent might end up at thepushworkflow, if both events are used together.(The interesting part about this image is that the "build-test PMD" run was created during "build-test on: pull request".
See also: https://github.saobby.my.eu.orgmunity/t/specify-check-suite-when-creating-a-checkrun/118380?u=jwgmeligmeyling
Split off from #2
The text was updated successfully, but these errors were encountered: