Automatically ✨, and not 🧠
Yes and no!
styler. Better paired with version control.
roxygen2 NAMESPACE generation. Switching:
pkgdown. Work on reference index & navbar!
Right after my talk (not now 😜), but then?
Run something every time you make a change
“The idea behind continuous integration is that CI will automatically run R CMD check (along with your tests, etc.) every time you push a commit to GitHub. You don’t have to remember to do this; CI automatically checks the code after every commit.” Julia Silge
GitHub Actions, Circle CI,
How to learn?
Julia Silge’s post - Jim Hester’s GitHub Actions talk -
LIFE HACK: My go-to strategy for getting Travis builds to work is snooping on *other* people's .travis.yml files. Shoutout today to the tidyr .travis.yml for solving my problem! #rstats 🙌— Julia Silge (@juliasilge) December 12, 2019
Couple a thing (R CMD check? pkgdown site building?) to
… each commit,
… every Monday,
… applying a label to a pull request?
precommit R package – Python precommit framework
Hooks for styling, parsable R code, spell checks, etc.
🤫 You can still skip the checks.
CRAN release! 🐉 Checks on different platforms, URLs, spell checks…
usethis::use_release_issue() creating a GitHub issue with important items.
Risk of spending too much time on meta-work.
As a beginner, easier to create good habits. 😉
You want to know what is going on.
You want to build on the function/package for your own goals.
You’re just curious.
You need examples of a thing in the wild.
Mirrors of CRAN packages and R-source, on GitHub.
And trying things out!
Fork, clone, and explore!
Podcast episode “Learning a new codebase”, with Patricia Aas
Blog posts: digested information.
R-hub blog, rOpenSci blog and tech notes
Fora: Help and learn.
R-package-devel, RStudio community “package development” category, rOpenSci forum.
💡 Manage your subscriptions & involvement wisely!
Transparent, constructive, non adversarial and open review process for packages in scope.
Also rOpenSci Statistical Software Peer Review.
Interesting for authors, and reviewers!
Online book of best practice for the reviews and package development.
See also JOSS, R Journal, JSS.
Write them in the shared doc.