How to work with action artefacts? Like, code coverage reports?

General
1

How do you store and present artefacts generated by actions, eg test or coverage reports? I’ve seen the suggestion to use the “general package” registry. Does somebody “link” that to builds, eg by using a build id? Do you clean up artefacts after some time?

Any hints are appreciated. Bonus for: Does somebody have “coverage badges” as SVG?

Regards,

Christian

2

After some research, I found this:

Github has a standard job summary feature, which is a Markdown file. While act does publish the env variable GITHUB_STEP_SUMMARY=/var/run/act/workflow/SUMMARY.md Gitea currently doesn use it.

eg this ticket: Actions - Job Summary · Issue #23721 · go-gitea/gitea · GitHub

Bottom line: No support today, but maybe Gitea will implement it the same way as Github does.