Fix discrepancy in git instructions

[hsaunders1904]

Description

These are some changes I made to the slides when delivering section 3/4 of the course in March.
Changes are:

• Fixed some out-of-date SSH addresses that still point to the UKAEA repository.
• Removed a slide at the end of section 3 that instructs students to merge their working branch into develop. This caused some confusion in section 4, where, in the first exercise, students are asked to create a pull request containing their changes, but they'd already merged them.

Looking at the notes now, I see that it says to open a PR into main not develop, but there was definitely some confusion on the day. It may have been my fault!

I need to check through the course notes to find the right answer here, but don't have the time right now. I'll try to have a look in the next few days.

[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/python-intermediate-development/compare/md-outputs..md-outputs-PR-462

The following changes were observed in the rendered markdown documents:

 common-issues.md                    |  2 +-
 md5sum.txt                          |  4 ++--
 section_4_collaborative_soft_dev.md | 10 +++++-----
 3 files changed, 8 insertions(+), 8 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-05-30 16:17:39 +0000

[bielsnohr]

Going to keep #458 open and make #464 be the one that closes it.