Make it possible for the release to use a renv.lock - #2195
Merged
Conversation
- the functionality was already there in form of the cfg$renvLockFromPrecedingRun - to make it less specific rename cfg$renvLockFromPrecedingRun to cfg$UseThisRenvLock - add cfg$renvLockFromPrecedingRun to the default.cfg
| #### Current CES parameter and GDX revision (commit hash) #### | ||
| cfg$CESandGDXversion <- "00013a4f0071f982a549e73748e50e45a02032e8" | ||
|
|
||
| #### Path to a renv.lock file to restore a project's dependencies from. If NULL, all R packages in their currently installed version will be used. |
Member
There was a problem hiding this comment.
yes, should be a configuration switch
dklein-pik
marked this pull request as ready for review
September 8, 2025 12:57
LaviniaBaumstark
approved these changes
Sep 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of this PR
Make it possible for the release (and any run) to use a renv.lock:
cfg$renvLockFromPrecedingRuncfg$renvLockFromPrecedingRuntocfg$UseThisRenvLockcfg$renvLockFromPrecedingRunto thedefault.cfgType of change
Parts concerned
Impact
Checklist
make test) after my final commit and all tests pass (FAIL 0)remind2if and where it was neededforbiddenColumnNamesin readCheckScenarioConfig.R in case the PR leads to deprecated switchesCHANGELOG.mdcorrectly (added, changed, fixed, removed, input data/calibration)