create action(s) for packages

[maxheld83]

These actually should be separate actions, because

1. they should run on (some yet to be chosen) vanilla image (not byod)
2. they should first parse and download the DESCRIPTION. We don't want people to have to specify the dependencies in the DESCRIPTION and their byod in this case. This (the parsing) may need some amount of bashing.

[maxheld83]

this issue is too big and will need to be broken down into smaller parts.

[maxheld83]

Now, let's break this down into smaller pieces, sorted roughly by kind and (loosely) order of execution:

Provisioning (for lack of a better term)

• choose an appropriate Docker image, or let the user provide one. provide good docker image for pkg devel #106

CI (narrowly defined)

• devtools::build() create action to build packages #121
• devtools::install() install r packages to $HOME, not $GITHUB_WORKSPACE #152
• devtools::check_built() use rcmdcheck #169
• ...?

"Programmatic Commits" (for lack of a better term)

• devtools::document() run devtools::document() #102 (being able to commit without roxygen build artefacts is a long-running pet peeve of myself)
• styler::style_pkg() run styler::style_pkg() on a repo #103
• run clang-format run clang-format #104
• automatically reorder description automatically reorder description #127
• tidy thanks / thank all contributors add action for tidythanks #128
• ...

These are, potentially, the most destructive / confusing, because they cause programmatic diffs.
But they can also save a lot of time and enforce strong quality control; probably most valuable for the tidyverse/r-hub teams (the focus here), not many other pkg devs.

Programmatic Code Review

• goodpractice::goodpractice() run goodpractice::goodpractice() #105
• lintr::lint_package() support linting #90
• covr::codecov() send results to codecov or (may need modifications to covr) run code coverage #107
• run r-hub and retrieve results add action for r-hub #71
• run benchmarking and other stats action to report performance stats #113
• run revdepcheck create action to run revdepcheck #123
• spellchecks! add action to spellcheck diffs #126
• ...

These are all essentially code review bots who write below commits and PRs via the github API.
They might be pretty cool and are something that might be uniquely easy to accomplish with github actions as opposed to other CI/CD.

Continuous Delivery (deploying artefacts somewhere)

• pkgdown::build_site() add pkgdown action #177
  • deploy to gh-pages avoid need for PAT for ghpages deploy #77 automatically get github pat for ghpages #16 (this already exists in another action of mine)
  • deploy to netlify (seems to have fans)
  • deploy to rsync (made this for another project, probably irrelevant here)
  • deploy to firebase (same)
• make a github release action to craft github release #108
• deploy to cran deploy to cran #109
• ...

[maxheld83]

structure and ideas in here are well documented in issues and labels.