Gábor Csárdi

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:...

I looked at https://github.com/NIEHS/amadeus/blob/main/.github/workflows/test-coverage-local.yaml but I am not sure if it is something that we can roll out. It has issues with concurrency as well, as it is pushing commits...

We could also store the coverage data in a designated branch on GH, called `coverage-data`. Then we would do a brute-force pull-commit-push-revert loop to avoid the concurrency issues. But storing...

As long as the codecov upload is working, and it should be working right now, we can use codecov as a DB, through its api, if we don't want to...

Related: I think it would be great to have some mappings from the `SystemRequirements` field in `DESCRIPTION` to the names of the corresponding libraries/tools on various platforms. Then the installer...

Try downloading the tarball or zip file from GitHub, extracting it and then calling `R CMD build` and `R CMD INSTALL`.

E.g. https://docs.python.org/2/library/os.path.html in Python. node.js has a bunch of them, they are pretty basic. I guess this is what you need most of the time. E.g. https://www.npmjs.com/package/fs-extra Edit: also, http://cran.r-project.org/web/packages/pathological/index.html

`save-always` was deprecated 4 days ago, so marking this as a bug seems a little excessive. :)

I wonder if this is something that could be configured by the end user, instead of the IDE and the package developer?

That typically happens if some cleaner process cleans up the temporary directory. I forgot how this works exactly, but we can probably make it more robust, still.