however that omits the job id of the action run and goes to the summary page. if there are multiple jobs within that workflow its very hard to say from which job report is correlated to
doesnt look like its trivial to add job id though as its not exposed as env var and there are other things to consider:
action might have multiple jobs so hitting API endpoint for all jobs might yield multiple job ids
as per https://docs.github.com/en/actions/learn-github-actions/variables#default-environment-variables we link to action id:
however that omits the job id of the action run and goes to the summary page. if there are multiple jobs within that workflow its very hard to say from which job report is correlated to
doesnt look like its trivial to add job id though as its not exposed as env var and there are other things to consider:
some useful urls
https://stackoverflow.com/questions/71240338/obtain-job-id-from-a-workflow-run-using-contexts https://github.com/orgs/community/discussions/123637 https://github.com/orgs/community/discussions/8945