You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of moving my package's, L0Learn, CI/CD to GitHub Actions. Currently, I am facing an issue where setup-r-dependencies fails because the R package is in a sub-directory of my repo.
The cause of this issue is found here as the directory that pak inspects for dependencies is hardcoded as local::.:
Error: Error: <callr_remote_error: Cannot install packages:
* local::.: No root directory found in /Users/runner/work/L0Learn/L0Learn or its parent directories. Root criterion: contains a file "DESCRIPTION" with contents matching "^Package: ">in process 20845
--><simpleError: Cannot install packages:
* local::.: No root directory found in /Users/runner/work/L0Learn/L0Learn or its parent directories. Root criterion: contains a file "DESCRIPTION" with contents matching "^Package: ">
I would be happy to submit a PR for this change, if this new functionality is deemed valuable.
Meanwhile, are there any workarounds for this issue?
The text was updated successfully, but these errors were encountered:
I am in the process of moving my package's, L0Learn, CI/CD to GitHub Actions. Currently, I am facing an issue where
setup-r-dependencies
fails because the R package is in a sub-directory of my repo.The cause of this issue is found here as the directory that
pak
inspects for dependencies is hardcoded aslocal::.
:actions/setup-r-dependencies/action.yaml
Line 24 in fd9a09a
I am rather new to using Github Actions, so I am unsure of which of these solutions (if any) would be better:
setup-r-dependencies
action aware of theworking-directory
parameter in the greater "workflow action scope"install_github
from devtools(https://www.rdocumentation.org/packages/devtools/versions/1.13.6/topics/install_github)I would be happy to submit a PR for this change, if this new functionality is deemed valuable.
Meanwhile, are there any workarounds for this issue?
The text was updated successfully, but these errors were encountered: