As far as I can tell there were no repo-specific tweaks to the standard GitHub actions, so I just re-ran the boiler-plate-setup functions from {usethis}, should be fine.
Can adjust afterwards if needed.
Also added the etm package to Config/Needs/website in DESCRIPTION, which flags is at a dependency for the website which the r-lib/actions/setup-r-dependencies actions picks it up during the workflow.
Alternative solution would be to explicitly add it as an explicit dependency to the pkgdown workflow, but that would be something to keep track of for future workflow file updates (such as this PR addresses).
As far as I can tell the Config/ entry is non-invasive and fairly robust in this context, see also: https://r-pkgs.org/dependencies-in-practice.html#sec-dependencies-nonstandard-config-needs
As far as I can tell there were no repo-specific tweaks to the standard GitHub actions, so I just re-ran the boiler-plate-setup functions from
{usethis}
, should be fine. Can adjust afterwards if needed.Also added the
etm
package toConfig/Needs/website
inDESCRIPTION
, which flags is at a dependency for the website which ther-lib/actions/setup-r-dependencies
actions picks it up during the workflow.Alternative solution would be to explicitly add it as an explicit dependency to the
pkgdown
workflow, but that would be something to keep track of for future workflow file updates (such as this PR addresses). As far as I can tell theConfig/
entry is non-invasive and fairly robust in this context, see also: https://r-pkgs.org/dependencies-in-practice.html#sec-dependencies-nonstandard-config-needs