Docs: Add rig instructions for R pre-release testing #244
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.
Incorporates suggestion from Issue #239 to document the use of 'rig add next' and 'R-next' for installing and switching to the development version of R.
Summary
Adds a new section to the Testing Pre-release R Versions chapter (
testing_pre_release_r_versions.qmd
) detailing the user-friendly commands for managing R's development version using the rig tool.rig add next
,R-next
, andrig default R-next
.bash
code blocks.Fixes #239
Checklist for adding a new chapter or chapters
What should a reviewer concentrate their feedback on?
Acknowledging contributors
List any contributions that need adding to the table of contributors. Common contributions are
content
(adding to the guide),doc
(e.g. README, wiki),infra
(e.g. GitHub action), andmaintenance
(e.g. fixing links). See the full key to Contribution Types.