search

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

Add branching episode #58

Closed avallecam closed 8 months ago

avallecam commented 8 months ago

Fixes #25

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-58

The following changes were observed in the rendered markdown documents:

 07-github.md                            |  17 +-
 08-collab.md                            |  37 ++--
 09-conflict.md                          | 290 ++++++++++++++++++++++----------
 14-supplemental-rstudio.md              |   8 -
 fig/github-branch-pullrequest.png (new) | Bin 0 -> 20685 bytes
 fig/github-commit-diff.png (new)        | Bin 0 -> 33412 bytes
 fig/github-commits-button.png (new)     | Bin 0 -> 110462 bytes
 md5sum.txt                              |  10 +-
 renv.lock                               |   4 +-
 9 files changed, 247 insertions(+), 119 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-03-05 21:36:49 +0000