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

Use renv for GHA #145

Open
wants to merge 4 commits into
base: dev
Choose a base branch
from
Open

Use renv for GHA #145

wants to merge 4 commits into from

Conversation

jthompson-arcus
Copy link
Collaborator

No description provided.

@jthompson-arcus
Copy link
Collaborator Author

@LDSamson full disclosure: I don't really know how r-lib/actions/setup-r-dependencies fully interacts with renv. I have had issues on other projects when using the public PPM instead of the repo specified in renv.lock. Some of these issues are hidden because of the package installation cache and don't show up until you add a new package with your snapshot date.

Also, I feel like r-lib/actions/setup-renv must be doing something different than the generic setup dependencies. Otherwise, why have two?

@LDSamson
Copy link
Collaborator

That interaction is a bit confusing for me as well. I think setup-r-dependencies does not use the renv.lock file to install exact versions. But I think it uses the standard local renv library storage, so it will install from there first if a package is available (at least that is my guess).

Better to use one I think indeed. I used setup-r-dependencies in addition to setup-renv as a (inefficient) way to install additional dependencies (e.g. covr), but these are now included in the full renv lockfile profile so what you propose here should be better I think.

Also, it's probably better to merge GHA workflow changes to main as well. No need to update the version I think since the actual code itself is not changing. What do you think?

@jthompson-arcus
Copy link
Collaborator Author

It is also not hard to just install a package if it's needed in the GHA. To me it makes more sense to be testing the package in the theoretical environment it is designed to be ran in. We can of course reconsider if we want to release on CRAN or we expect people to be downloading directly from GitHub as opposed to forking/cloning the project.

I'm not so concerned about merging it to main by itself. We can but I don't really see it as a value add. More important on the development side of things.

@jthompson-arcus jthompson-arcus marked this pull request as ready for review December 4, 2024 17:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants