Closed oxc closed 2 months ago
The Action creates a new status check and the Action doesn't have control where that is displayed in the UI as far as I know. Do you have any suggestions on what the Action can do differently that would help resolve your issue?
Thanks for your reply. You're right, this seems to be an issue in Github that many people are complaining about: https://github.community/t/github-actions-status-checks-created-on-incorrect-check-suite-id/16685
According to this thread, there does not seem to be a solution at the moment (using a Github App instead of an Action seems to be "the way").
Related threads:
Feel free to close this, or keep it open for whenever this might be possible to implement.
Can't this be solved with setting an external_id when creating the check?
@noamgolani can you elaborate on how external_id
would tie the status check to a job in the UI?
The above linked docs say.
external_id
string A reference for the run on the integrator's system.
That must be a reference to CI-s running outside GitHub Actions.
Closing this as I don't think there is anything I can do.
Also dropping a note that 3.0.0
has been released. Please update any references to the v3
branch instead of v3-beta
. Make sure to read the Changeling as there are breaking changes (GH_TOKEN input has changed)
I have multiple workflows that get triggered on pull_request. One of them is called "Run tests for pull request" and has a job called "Run linter" that runs the
eslint-annotate-action
.However, the annotations often show up as child of a completely unrelated workflow. It seems undeterministic under which workflow it shows up.
In the following example, the annotation results wrongly show up as part of the "Code coverage" workflow:![image](https://user-images.githubusercontent.com/1388972/148072259-a2d90776-1cb1-41e2-861f-d49640211a1d.png)
Here is an excerpt from the workflow that runs the action: