Initial version of the gh-action ready for release

[epijim]

Primary aims in this release:

• - Run R CMD check (check installation)
• - Run covr::package_coverage() (check unit test coverage)
• - Run covtracer (link documentation to unit tests)
• - Place results into pdf report
• - User can have this report automatically appended to a release tag

This is tracked in meta-issue #8, and this milestone

---

This discussion was created from the release Initial version of the gh-action ready for release.

[epijim]

Does this gh-action provide a level of 'trust' in the package building as intended that is at least equal to CRAN - for that point, I believe we have reached that threshold.

Check	CRAN	thevalidatoR
R CMD check (>50 individual structural and build checks)	YES	YES
Human scan of package novelty / is not trivial	YES - although has been flagged as variable	NO - fully automated so no human scan
Update frequency limits	YES	NO
Test environments	Multiple, but not clear exactly what build environments	Defaults to versioned rocker
Document package coverage	NO	YES
Document linking of capabilities to testing	NO	YES

[kieranjmartin]

The one thing I think might be missing here is dependency vs reverse dependency checks. Maybe reverse dependency checking isn't really needed if the goal is just to demonstrate that the package is reliable, but it is something CRAN enforces.

[gowerc]

I think on the same vein as what @kieranjmartin said but yer CRAN makes sure that all the latest versions of packages are fully compatible with each other on both the current and development versions of R. Rocker has fixed packages versions as of the date of the release of the corresponding R version. If memory serves me right CRAN forces you to show the R CMD CHECK results for all the packages that are dependent on yours before you can update it.