You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Per...
For further actions, you may consider blocking this person and/or reporting abuse
Nice set of workflows. I haven't used Perl in a long time, but I use GitHub Actions for similar purposes for Java. I have a few ideas based on things I do that might be useful for your coverage workflow.
It might be useful to use
actions/upload-artifactafter generating the coverage report to attach the report to the GitHub Actions run. If you want to examine report, you can then download from the Actions tab.I find it useful to comment coverage on PRs. I think there are Actions you can use for that. But I just use the GitHub cli in a step of my workflow. It's available to workflows by default. Useful for other things too, but for commenting on a PR the command is
gh pr comment PR-NUMBER -b "Your comment". You can use markdown in the comment string. In some of my Java projects, my workflow comments the coverage percentage and the branches coverage.Thanks for the suggestions. I definitely have plans for making the results from these workflows easier to see. And artifacts and/or comments will certainly be part of that.