insightsengineering/Dependency Test

Resolve package dependencies according to the strategy used, install them and execute R CMD CHECK

Trust Signals

workflow.ymlSHA-pinned

uses: insightsengineering/r-verdepcheck-action@0bbf95f97ae3d6018e8cde78e4febd61f3805d50 # v0.2.0

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
github-token	Token with permissions to clone repositories with dependencies.	no	""
repository-path	Directory where the checked package has been cloned.	no	.
extra-deps	Extra dependencies specified similarly as in the `DESCRIPTION` file, i.e. `"<package name> (<operator> <version>)"` where both `<operator>` and `<version>` are optional. Multiple entries are possible separated by `";"`.	no	""
check-args	Optional value of args argument to rcmdcheck::rcmdcheck in form of a string with space as delimeter, e.g. "--no-examples --no-tests".	no	""
build-args	Optional value of build_args argument to rcmdcheck::rcmdcheck in form of a string with space as delimeter, e.g. "--force --keep-empty-dirs".	no	""
strategy	Strategy to test package dependencies. One of: min_isolated, min_cohort, release, max.	yes	—
additional-env-vars	Additional environment variables. Example usage: additional-env-vars: \| ABC=123 XYZ=456	no	""
additional-repos	Optional value that add R repositories for a given strategy. Multiple entries are possible separated by `";"`. Example usage: `additional-repos: https://repo1.example.com;https://repo2.example.com`	no	""

no outputs