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

Propagate renv.lock from pharmaverse/admiralci #53

Merged
merged 2 commits into from
Sep 6, 2023

Conversation

pharmaverse-bot
Copy link
Collaborator

This PR has been automatically generated by renv.lock propagation workflow from pharmaverse/admiralci.

Please review the changes.

@github-actions
Copy link

github-actions bot commented Aug 16, 2023

Code Coverage

Package Line Rate Health
pharmaversesdtm 0%
Summary 0% (0 / 41)

@kaz462
Copy link
Contributor

kaz462 commented Aug 28, 2023

@bundfussr @bms63 do we need to merge this PR for the upcoming release?

@bundfussr
Copy link
Contributor

@bundfussr @bms63 do we need to merge this PR for the upcoming release?

In principle, yes because it ensures that the renv.lock is consistent across the repositories. However, the R-CMD checks are failing. So an update is required. @galachad , are you aware of this?

@galachad galachad merged commit d5aa097 into devel Sep 6, 2023
20 checks passed
@galachad galachad deleted the automated-renv-lock-propagation@devel branch September 6, 2023 07:01
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.

4 participants