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

Install sandpaper from custom fork #57

Closed Bisaloo closed 9 months ago

Bisaloo commented 9 months ago

cc @avallecam

github-actions[bot] commented 9 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-57

The following changes were observed in the rendered markdown documents:

 config.yaml | 2 ++
 md5sum.txt  | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)
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 16:44:29 +0000

avallecam commented 9 months ago

thank you for this edit, I did not notice that this was pending in the non-generative content lessons. Just made the corresponding edit in research compendium https://github.com/epiverse-trace/research-compendium/pull/37