: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:
The following changes were observed in the rendered markdown documents:
appendix.md (new) | 173 ++++++++++++++++
beforestart.md (new) | 54 +++++
compendium.md (new) | 195 ++++++++++++++++++
config.yaml | 7 +
fig/add_dependencies-github.png (new) | Bin 0 -> 78964 bytes
fig/citation-cff.png (new) | Bin 0 -> 60448 bytes
fig/code_of_conduct.png (new) | Bin 0 -> 10471 bytes
fig/concept-map-00.png (new) | Bin 0 -> 356197 bytes
fig/concept-map-01.png (new) | Bin 0 -> 197601 bytes
fig/concept-map-02.png (new) | Bin 0 -> 315882 bytes
fig/concept-map-03.png (new) | Bin 0 -> 275707 bytes
fig/description-title.png (new) | Bin 0 -> 40352 bytes
fig/folder_mess_cooking.png (new) | Bin 0 -> 522284 bytes
fig/folder_tidy_cooking.png (new) | Bin 0 -> 524812 bytes
fig/fun-demo-web.png (new) | Bin 0 -> 59687 bytes
fig/fun-demo.png (new) | Bin 0 -> 146049 bytes
fig/git-revert.png (new) | Bin 0 -> 12061 bytes
fig/goal-intro.png (new) | Bin 0 -> 320212 bytes
fig/helpful_resources.png (new) | Bin 0 -> 3351 bytes
fig/issue_template-content.png (new) | Bin 0 -> 57879 bytes
fig/issue_template.png (new) | Bin 0 -> 20721 bytes
fig/markdown-header.png (new) | Bin 0 -> 10539 bytes
fig/markdown-readme.png (new) | Bin 0 -> 45114 bytes
fig/project-init.png (new) | Bin 0 -> 67970 bytes
fig/projectname-01-github.png (new) | Bin 0 -> 72716 bytes
fig/projectname-01.png (new) | Bin 0 -> 40623 bytes
fig/push-and-pull.png (new) | Bin 0 -> 89387 bytes
fig/readme-github.png (new) | Bin 0 -> 50853 bytes
fig/readme_so-preview.png (new) | Bin 0 -> 28947 bytes
fig/readme_so-sections.png (new) | Bin 0 -> 35666 bytes
fig/renv.png (new) | Bin 0 -> 32188 bytes
fig/reproducible_analysis.png (new) | Bin 0 -> 291231 bytes
fig/rrtools-paper.png (new) | Bin 0 -> 20171 bytes
fig/rrtools-templates.png (new) | Bin 0 -> 31191 bytes
introduction.md (new) | 91 +++++++++
md5sum.txt | 11 +-
readmefile.md (new) | 289 ++++++++++++++++++++++++++
reproducible.md (new) | 374 ++++++++++++++++++++++++++++++++++
setup.md | 2 +-
wrapup.md (new) | 80 ++++++++
40 files changed, 1273 insertions(+), 3 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.
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/research-compendium/compare/md-outputs..md-outputs-PR-3
The following changes were observed in the rendered markdown documents:
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 2023-09-03 21:24:24 +0000