github-actions[bot]
commented
1 year 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:
- :dart: correct output
- :framed_picture: correct figures
- :question: new warnings
- :bangbang: new errors
Rendered Changes
:mag: Inspect the changes: https://github.com/datacarpentry/R-ecology-lesson/compare/md-outputs..md-outputs-PR-867
The following changes were observed in the rendered markdown documents:
00-before-we-start.md | 23 +-
05-r-and-databases.md | 2 +-
config.yaml (gone) | 86 --
...tion-ggplot2-rendered-boxplot-with-points-1.png | Bin 79416 -> 78822 bytes
...ization-ggplot2-rendered-unnamed-chunk-10-1.png | Bin 97851 -> 98061 bytes
...ization-ggplot2-rendered-unnamed-chunk-11-1.png | Bin 64734 -> 64968 bytes
...lization-ggplot2-rendered-unnamed-chunk-9-1.png | Bin 82845 -> 82526 bytes
index.md | 7 +
md5sum.txt | 34 +-
renv.lock (gone) | 1575 --------------------
10 files changed, 37 insertions(+), 1690 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 2023-07-10 13:54:37 +0000
Since @datacarpentry/curriculum-advisors-ecology published their call for beta pilots and feedback on the redesigned version of this lesson in the Incubator.