github-actions[bot]
commented
2 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:
- :dart: correct output
- :framed_picture: correct figures
- :question: new warnings
- :bangbang: new errors
Rendered Changes
:mag: Inspect the changes: https://github.com/UCL-ARC/r-amr-epidemiology/compare/md-outputs..md-outputs-PR-30
The following changes were observed in the rendered markdown documents:
01-rstudio-intro.md | 2 +-
02-project-intro.md | 2 +-
26-log-regression.md | 9 +-
27-sql-r.md (new) | 71338 +++++++++++++++++++
cdrcDB.sqlite (new) | Bin 0 -> 14069760 bytes
data/AHAH_V3_0.csv (new) | 41730 +++++++++++
data/ahah_data_profile.pdf (new) | Bin 0 -> 224711 bytes
data/uk_imd2019.csv (new) | 42620 +++++++++++
fig/23-statistics-rendered-unnamed-chunk-3-1.png | Bin 4728 -> 4531 bytes
fig/23-statistics-rendered-unnamed-chunk-3-2.png | Bin 5111 -> 4601 bytes
...nreg-diagnostics-rendered-unnamed-chunk-8-1.png | Bin 24444 -> 24481 bytes
fig/joins.png (new) | Bin 0 -> 265289 bytes
md5sum.txt | 7 +-
13 files changed, 155698 insertions(+), 10 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-09-04 11:10:56 +0000
New pull request as it wasn't finding the questions section