Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setup-r-dependencies to accept working-directory or similar functionality #438

Closed
TNonet opened this issue Nov 17, 2021 · 1 comment · Fixed by #441
Closed

Allow setup-r-dependencies to accept working-directory or similar functionality #438

TNonet opened this issue Nov 17, 2021 · 1 comment · Fixed by #441

Comments

@TNonet
Copy link
Contributor

TNonet commented Nov 17, 2021

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::.:

saveRDS(pak::pkg_deps("local::.", dependencies = TRUE), ".github/r-depends.rds")

I am rather new to using Github Actions, so I am unsure of which of these solutions (if any) would be better:

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?

@github-actions
Copy link

github-actions bot commented Nov 6, 2022

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant