epiverse-trace / git-rstudio-basics

Version Control with Git using Rstudio
https://epiverse-trace.github.io/git-rstudio-basics/
Other
1 stars 0 forks source link

Update 2 packages #55

Closed Bisaloo closed 3 weeks ago

Bisaloo commented 8 months ago

:robot: This is an automated build

This will update 2 packages in your lesson with the following versions:

# CRAN -----------------------------------------------------------------------
- renv   [1.0.3 -> 1.0.5]
- xfun   [0.41 -> 0.42]

:stopwatch: In a few minutes, a comment will appear that will show you how the output has changed based on these updates.

If you want to inspect these changes locally, you can use the following code to check out a new branch:

git fetch origin update/packages
git checkout update/packages
github-actions[bot] commented 8 months ago

Thank you!

Thank you for your pull request :smiley:

:robot: This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

Rendered Changes

:mag: Inspect the changes: https://github.com/epiverse-trace/git-rstudio-basics/compare/md-outputs..md-outputs-PR-55

The following changes were observed in the rendered markdown documents:

 md5sum.txt |   2 +-
 renv.lock  | 149 +++++++++++++++++--------------------------------------------
 2 files changed, 43 insertions(+), 108 deletions(-)
What does this mean? If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

:stopwatch: Updated at 2024-10-01 00:53:04 +0000