draft 3rd episode

[erwinlares]

@martinherrerias

I have been working on Episode 3 on my own. I realized today that you have added some content too. Would you review my edits, please.

Closes #7

[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-26

The following changes were observed in the rendered markdown documents:

 03-reproducible-dev-environment.md | 644 +++++++++++++++++++++----------------
 md5sum.txt                         |   2 +-
 2 files changed, 360 insertions(+), 286 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 2025-11-25 18:56:31 +0000

[martinherrerias]

Hi @erwinlares, any chance you could rewrite your changes without the word-wrap? i.e. removing:

editor_options: 
  markdown: 
    wrap: 72

I understand it makes it easier to edit, but it doesn't play well with version control. It makes it really hard for me (and git) to see what actually changed. Similarly, any "linting" changes like switching all ::::...'s to :::, should either be dropped, or be in a different commit than actual content changes.