Automatically ✨, and not 🧠
Yes and no!
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
Travis, GitHub Actions, Circle CI,
How to learn?
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?
Hooks for styling, parsable R code, spell checks, etc.
🤫 You can still skip the checks.
CRAN release! 🐉 Checks on different platforms, URLs, spell checks…
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.
And trying things out!
Fork, clone, and explore!
Blog posts: digested information.
Fora: Help and learn.
💡 Manage your subscriptions & involvement wisely!
Interesting for authors, and reviewers!
Online book of best practice for the reviews and package development.
🚀 Even more review and best practice on the way! rOpenSci Statistical Software Peer Review
See also JOSS, R Journal, JSS.
Write them in the shared doc.