Switch code review PR target to be develop branch rather than main

[bielsnohr]

In the "Raising a Pull Request" section of Episode 4.1, the target branch for the PR is set to be main. If we are following "gitflow" like in the rest of the lesson, this should be develop. This has directly caused confusion in our runs of the course and I don't think it should cause any issues, although there might be some merge conflicts because the develop branch has had quite a bit done to it by this point, and the feature-std-dev branch is quite far behind.

I will report back how it goes, but if someone is able to resolve this more immediately, that would be appreciated.

Resolves #458

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

The following changes were observed in the rendered markdown documents:

 41-code-review.md | 2 +-
 md5sum.txt        | 2 +-
 2 files changed, 2 insertions(+), 2 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:09:29 +0000