Add the analogy of pull requests and editing a shared document

[anenadic]

Fixes #463.
Will crate a separate issue to create a diagram for a PR collaboration workflow.

[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/lesson-development-training/compare/md-outputs..md-outputs-PR-469

The following changes were observed in the rendered markdown documents:

 collaborating-team.md | 6 ++++++
 md5sum.txt            | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

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-04 11:25:53 +0000

[tobyhodges]

Thanks @anenadic, I like this a lot.

Please could you adjust to use sentence line breaks before we merge?

[tobyhodges]

Great, thank you!