Add collaborative git

[lyashevska]

About

This PR moves Collaborative Version Control episode into git-lesson

Changes

• Added a markdown file with teaching content.
• Added 03-collaborative-git.md to config.yaml

Review instructions

Requirements

See carpentries workbench requirements

Instructions

Follow steps outlined in the file.

Related issues

• Move Collaboration with git to the new workbench lesson esciencecenter-digital-skills/good-practices-in-research-software-development#37

[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/esciencecenter-digital-skills/git-lesson/compare/md-outputs..md-outputs-PR-2

The following changes were observed in the rendered markdown documents:

 03-collaborative-git-centralized.md (new) | 63 +++++++++++++++++++++++++++++++
 03-collaborative-git-distributed.md (new) | 58 ++++++++++++++++++++++++++++
 config.yaml                               |  2 +
 md5sum.txt                                |  4 +-
 4 files changed, 126 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-03-28 11:11:38 +0000

[svenvanderburg]

Looks good! I left a few comments. At this point it is not really useful as standalone material, but I don't think that is the aim here.

I would suggest to split this into 2 episodes: one on centralized workflow and one on distributed workflow. So they match a bit more in terms of length and cognitive load the 7 episodes in the SWC git intro part.

Feel free to do with my feedback what you want and then merge!

[lyashevska]

Great, thanks for your feedback. I guess the solution part should be left empty.

[lyashevska]

This closes esciencecenter-digital-skills/good-practices-in-research-software-development#37