Display result summary when using workflow_dispatch or schedule

[Fgerthoffert]

Hi,

Is there a way to get results displayed in the summary when tests are triggered using workflow_dispatch or schedule ?

When the trigger is a change in code, the results are shown in the run summary.

Using workflow_dispatch or schedule, the results are still visible in the action logs, but it would be super helpful if they could be brought up to the summary.

  ℹ️ 137 tests run, 2 skipped, 3 failed.
  ℹ️ Posting with conclusion 'failure' to refs/heads/master (sha: 31719493de9c531f39891431db477a3f8393989

Thanks,

[mikepenz]

@Fgerthoffert thank you for the ticket.

It could be that when actions are part of a workflow_dispatch trigger, that the contained github context points towards the wrong repo.

As you can see here the github API is used to create the checks / update the checks on the repo according to the github context:
https://github.com/mikepenz/action-junit-report/blob/main/src/main.ts#L105-L134

It could also be that the token is just not having the right scope in such cases resulting in it not being allowed to add the checks.

Is the run you referenced visible open source?

[Fgerthoffert]

Thanks for the quick response @mikepenz

The particular repo this was happening on is not open-source, but the same workflow is soon going to be ported over to some of our public repos, once done I'll update this issue with links to some runs.

In the meantime, I will enable debug to see if I can get more data from the content of createCheckRequest

[mikepenz]

Thank you very much.

[Fgerthoffert]

Out of curiosity, did you consider using core.notice(), core.warning() or core.error() instead of manually creating an annotation via octokit?

https://github.com/actions/toolkit/blob/main/packages/core/README.md#annotations

I'm using it on a small action and it does show the annotation for jobs triggered via workflow_dispatch or schedule.

[mikepenz]

No we didn't use that one yet.
Potentially worth a try, not sure on it's performance though compared to the API request