Helpers for tidyverse developmentSource:
These helpers follow tidyverse conventions which are generally a little stricter than the defaults, reflecting the need for greater rigor in commonly used packages.
use_tidy_github_actions(ref = NULL) use_tidy_upkeep_issue(year = NULL) create_tidy_package(path, copyright_holder = NULL) use_tidy_description() use_tidy_dependencies() use_tidy_eval() use_tidy_contributing() use_tidy_support() use_tidy_issue_template() use_tidy_coc() use_tidy_github() use_tidy_style(strict = TRUE)
Desired Git reference, usually the name of a tag (
"v2") or branch (
"main"). Other possibilities include a commit SHA (
"HEAD"(meaning "tip of remote's default branch"). If not specified, defaults to the latest published release of
Approximate year when you last touched this package. If
NULL, the default, will give you a full set of actions to perform.
A path. If it exists, it is used. If it does not exist, it is created, provided that the parent path exists.
Name of the copyright holder or holders. This defaults to "package name authors"; you should only change this if you use a CLA to assign copyright to a single entity.
Boolean indicating whether or not a strict version of styling should be applied. See
use_tidy_github_actions(): Sets up the following workflows using GitHub Actions:
R CMD checkon the current release, devel, and four previous versions of R. The build matrix also ensures
R CMD checkis run at least once on each of the three major operating systems (Linux, macOS, and Windows).
Report test coverage.
Build and deploy a pkgdown site.
This is how the tidyverse team checks its packages, but it is overkill for less widely used packages. Consider using the more streamlined workflows set up by
create_tidy_package(): creates a new package, immediately applies as many of the tidyverse conventions as possible, issues a few reminders, and activates the new package.
use_tidy_dependencies(): sets up standard dependencies used by all tidyverse packages (except packages that are designed to be dependency free).
use_tidy_description(): puts fields in standard order and alphabetises dependencies.
use_tidy_eval(): imports a standard set of helpers to facilitate programming with the tidy eval toolkit.
use_tidy_style(): styles source code according to the tidyverse style guide. This function will overwrite files! See below for usage advice.
use_tidy_contributing(): adds standard tidyverse contributing guidelines.
use_tidy_issue_template(): adds a standard tidyverse issue template.
use_tidy_release_test_env(): updates the test environment section in
use_tidy_support(): adds a standard description of support resources for the tidyverse.
use_tidy_coc(): equivalent to
use_code_of_conduct(), but puts the document in a
use_tidy_github(): convenience wrapper that calls
use_tidy_upkeep_issue()creates an issue containing a checklist of actions to bring your package up to current tidyverse standards.
Warning: This function will overwrite files! It is strongly suggested to only style files that are under version control or to first create a backup copy.
Invisibly returns a data frame with one row per file, that indicates whether styling caused a change.