Draft ep3

[sstevens2]

No description provided.

[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/better-research-software-r/compare/md-outputs..md-outputs-PR-39

The following changes were observed in the rendered markdown documents:

 03-reproducible-dev-environment.md | 282 +++++++++++--------------------------
 md5sum.txt                         |   3 +-
 2 files changed, 84 insertions(+), 201 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 2026-03-11 15:13:39 +0000

[sstevens2]

A few small changes and typos I suggested fix.

One thing I couldn't really add suggestions for was telling the story of setting up the renv part. Right now it is written a bit more like a manual in that it tells you what you might do. For the lesson, it would be helpful to walk users/instructor through a specific usage for this lesson repo. So tell them what commands to run to set it up. The instructions as they are don't actually tell us what to run for creating the renv and lock file, just hypothetically how to.