Action adds its check to the wrong workflow if it is re-run about accessibility-insights-action HOT 5 CLOSED

I wonder if this is related to https://github.community/t/specify-check-suite-when-creating-a-checkrun/118380 - the create-check-run endpoint doesn't offer a suite ID option, so the linking is managed by GitHub:

annotations generated in a Github action during a step executed in the “pull request” event, end up in the “workflow” for the "push’ event. Through hoops, it is possible to find the check run ID during a Github Action ... However, there is no way to specify the Check Suite ID when creating a new check run (its ignored in the request) and neither there seems to be any dedicated endpoint for creating check runs for a particular check suite.

from accessibility-insights-action.

changing to needs investigation per conversation with @peterdur

from accessibility-insights-action.

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

from accessibility-insights-action.

From @dbjorge
There isn't anything meaningful we can do on our end about the issue right now unless we move away from using check runs entirely - they're a "best of bad options" in terms of how we can present formatted summary output from our action as part of a GitHub Actions workflow.
Note: There is more info to this thread.

from accessibility-insights-action.

The check-run has been removed, therefor the Accessibility Insights Team is marking this bug as obsolete/closed

from accessibility-insights-action.