Join 📚 James's Highlights
A batch of the best highlights from what Jimmy's read, .
CRAN has a submission checklist, and you could either roll your own or rely on usethis::use_release_issue() creating a GitHub issue with important items. If you don’t develop your package on GitHub you could still have a look at the items for inspiration. The devtools::release() function will ask you whether you ran a spell check.
Workflow automation tools for package developers
Maëlle Salmon
Using roxygen2 is generally handy, starting with your no longer needing to edit the NAMESPACE by hand. If your package doesn’t use roxygen2 yet, you could use Rd2roxygen to convert the documentation.
Workflow automation tools for package developers
Maëlle Salmon
set through environment variable R_CHECK_ENVIRON with a command similar to
export R_CHECK_ENVIRON = <path to downloaded file>
Bioconductor - Package Guidelines
None
...catch up on these, and many more highlights
Readwise