Add refactoring lesson

[connoraird]

Closes #32

[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/UCL-ARC/fortran-unit-testing-lesson/compare/md-outputs..md-outputs-PR-33

The following changes were observed in the rendered markdown documents:

 ...o-to-unit-tests.md => 1-what-is-a-unit-tests.md |   18 +-
 2-intro-to-fortran-unit-tests.md (gone)            |   84 --
 2-refactor-fortran.md (new)                        | 1341 ++++++++++++++++++++
 config.yaml                                        |    6 +-
 index.md                                           |    4 +-
 md5sum.txt                                         |   10 +-
 setup.md                                           |    5 -
 7 files changed, 1359 insertions(+), 109 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-04 10:01:55 +0000