Open hadley opened 1 month ago
I am not really sure what you mean by this. That workflow has a lot of stuff. We don't necessarily need to provide ready to use workflows for everybody, but rather the actions that people can use to build their own workflows.
Re https://github.com/r-lib/actions/issues/834, is codecov upload still a problem?
Right, I was thinking that we don't actually use the actual service that much, and if it wasn't too hard to generate and save the data locally, maybe it's worth doing?
We can save the data as an artifact and/or print it, but it is a bit cumbersome to look at it.
We could print a summary to the terminal:
<img width="1189" alt="Screenshot 2024-05-25 at 8 38 13 PM" src="https://github.com/r-lib/actions/assets/660288/4a5e2e85-592d-4d46-a650-9bb1ee76fa0c"> But the missing lines column cannot have links, and that column must be probably truncated. Of course we also cannot browse the source code with coverage information.
We could try to create a Markdown summary for it, maybe, like this: https://github.com/marketplace/actions/code-coverage-summaryy#markdown-example We can link the missing lines, but still need to truncate them, and cannot browse code with coverage info.
Third possibility is to create an artifact with the coverage report, but that's also a but cumbersome to download, uncompress and then open locally.
Really, the ideal situation would be if codecov.io worked a bit better, and now that we are updating it properly, hopefully it will. It gives us coverage over time and badges, and you can browse the code with coverage info.
Btw. you need to update to the latest test-coverage
workflow to update.
Btw.2. there is a codecov extension for Chrome and Firefox, which is OK, then you can browse code on GH, with coverage info: https://github.com/codecov/codecov-browser-extension Unless you use another browser of course.
e.g. https://github.com/NIEHS/amadeus/blob/main/.github/workflows/test-coverage-local.yaml
Makes it easier for federal government to use and avoids problems like #834