Get started.
use_precommit(
path_cp_config_from = getOption("precommit.path_cp_config_from"),
force = FALSE,
open = rstudioapi::isAvailable(),
path_root = here::here()
)
Path or URL to a .pre-commit-config.yaml
. This config file
will be hard-copied into path_root
. If NULL
, we use
a default config from the path returned by
system.file("pre-commit-config.yaml", package = "precommit")
. See
section 'Copying an existing config file'.
Whether to replace an existing config file.
Whether or not to open the .pre-commit-config.yaml after
it's been placed in your repo. The default is TRUE
when working in
RStudio. Otherwise, we recommend manually inspecting the file.
The path to the root directory of your project.
You want to add pre-commit support to a git repo which does not have a
.pre-commit-config.yaml
. This involves adding
a pre-commit config file and making sure git will call the hooks before
the next commit.
You cloned a repo that has a .pre-commit-config.yaml
already. You need
to make sure git calls the hooks before the next commit.
installs pre-commit in your current directory.
sets up a template .pre-commit-config.yaml
.
autoupdates the template to make sure you get the latest versions of the hooks.
Open the config file if RStudio is running.
You can use an existing .pre-commit-config.yaml
file when intiializing
pre-commit with use_precommit()
using the argument path_cp_config_from
to copy
an existing config file into your repo. This argument
defaults to the R option precommit.path_cp_config_from
, so you may want to
set this option in your .Rprofile
for convenience.
Note that this is not equivalent
to the --config
option in the CLI command pre-commit install
and similar,
which do not copy a config file into a project root (and allow to put it
under version control), but rather link it in some more or less transparent
way.
Other helpers:
open_config()