episode 2 ready for website review

[peterlaurin]

:)

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 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:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/carpentries-incubator/R-help-reprexes/compare/md-outputs..md-outputs-PR-99

The following changes were observed in the rendered markdown documents:

 2-identify-the-problem.md                          |   73 +-
 config.yaml (new)                                  |   81 +
 ...e-problem-rendered-unnamed-chunk-11-1.png (new) |  Bin 0 -> 4846 bytes
 ...e-problem-rendered-unnamed-chunk-15-1.png (new) |  Bin 0 -> 8000 bytes
 ...e-problem-rendered-unnamed-chunk-16-1.png (new) |  Bin 0 -> 8267 bytes
 ...e-problem-rendered-unnamed-chunk-17-1.png (new) |  Bin 0 -> 20238 bytes
 ...he-problem-rendered-unnamed-chunk-9-1.png (new) |  Bin 0 -> 12745 bytes
 md5sum.txt                                         |    2 +-
 renv.lock (new)                                    | 1622 ++++++++++++++++++++
 9 files changed, 1774 insertions(+), 4 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.

⏱️ Updated at 2024-12-31 22:14:48 +0000

[kaijagahm]

let's take a look at it on the website!