GitHub Actions provides GITHUB_STEP_SUMMARY for writing a Markdown summary that appears with the run. Tell reviewers what ran, which configuration it used and where to find the full report.
Test the failure path
Verify a successful run and a controlled failure. If the report should run after a failure, set the reporting step’s condition accordingly and confirm the original failure remains visible. Keep secrets and sensitive test data out of summaries.
Give reviewers a result they can verify
A useful summary answers three questions before asking someone to download an artifact. Which commit and configuration ran, what passed or failed, and where is the detailed evidence? Keep those details next to the result so a reviewer can tell two retries apart.
A Bash step can append a fixed heading with printf followed by a newline and redirect it to the quoted GITHUB_STEP_SUMMARY path. Add the test totals produced by your test runner and a link to the uploaded report when available. Use data from the same run rather than hard-coding a passing message. Keep verbose logs in the artifact and use the summary to guide the reader to the failing case.
Suppose a run executes 120 tests and two fail. The summary should name the failed suite, show those totals and identify the report. If the test command stops the job before the summary is written, review the reporting step’s condition and give it an appropriate failure-path condition. Preserve the test command’s failure so the job remains red.
Verify with a known passing case and an intentional failing case. In each, open the run summary, follow the report link and compare its totals with the test log. A report that is easy to find still needs to belong to the correct commit and configuration.