Replies: 12 comments 2 replies
|
This issue was reported in Oct. 2019 and we're still waiting for a fix as of May 2022. |
|
Any word on this? When a developer views a workflow and does not see the checks that should be associated with it, it slows them down when they have to hunt for the results. Any way we can get this prioritized? Is there a tracking ticket? |
|
It would be helpful if you could provide some scenarios that you are trying to accomplish by creating your own check_runs. With the job summaries feature and directly creating annotations on the current job via the issue workflow command, I don't have any good additional ones in mind. |
|
This issue is particularly prevelant when using workflow_dispatch. |
|
Also running into this issue, still no updates on this? |
|
I'm also hitting this issue. Do you have any updates or possible workarounds? Thanks My use-case: I'm running some custom actions |
|
@chrispat our use case: We have a bunch of workflows running across various environments, see e.g. this tests_primary.yml. Once the tests from one of the workflows finish we need to collect all their result artifacts and produce aggregated test report which is then published to the PR that triggered the checks. Since we need access to the secrets to upload the report, the report generator runs in its own workflow create_test_report.yml which is triggered by
We need this check to either be shown at the top level next to the workflow runs or at least a way to specify which workflow_run it should be displayed under. |
|
👋 Hitting the issue too, any advice GitHub ? Ability to specify the check suite would be a nice workaround 👍 |
|
Facing the same issue, |
|
Running into the same issue, would really appreciate GitHub supporting this use case. It's a clear value add than a bunch of developers are trying to take advantage but running into the same issue. The idea that check runs are meant for apps besides GitHub actions (if that's even the case, it's hard to tell) seems like such an arbitrary miss. |
|
This has been tripping us up too, I want to post either |

Uh oh!
There was an error while loading. Please reload this page.
There is a super old issue that affects manually created check runs, see: https://github.community/t/github-actions-status-checks-created-on-incorrect-check-suite-id/16685, https://github.community/t/specify-check-suite-when-creating-a-checkrun/118380
POST /repos/{owner}/{repo}/check-runsadds checks to the incorrect check suite when called from GitHub actions. This creates quite a confusion in the status of our actions.It would be great if we could specify workflow run id (or check suite id) when creating a check run.
All reactions