fix: update screenshots

[amangoel185]

• Update screenshots for GitHub and VS Code setup
• Fixes GitHub UI has changed and new screen shots are needed #289 and updates feat: add callout to set venv in VS Code #329

[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/better-research-software/compare/md-outputs..md-outputs-PR-341

The following changes were observed in the rendered markdown documents:

 02-better-start-version-control.md     |   8 ++++----
 fig/github-copy-commands.png (new)     | Bin 0 -> 247457 bytes
 fig/github-create-new-repo.png (new)   | Bin 0 -> 175652 bytes
 fig/github-create-repository.png (new) | Bin 0 -> 121575 bytes
 fig/github-repository-name.png (new)   | Bin 0 -> 183739 bytes
 fig/vscode-interpreter-path.png        | Bin 539453 -> 305508 bytes
 fig/vscode-interpreter-venv.png        | Bin 853717 -> 625369 bytes
 fig/vscode-select-interpreter.png      | Bin 508721 -> 368603 bytes
 md5sum.txt                             |   3 +--
 9 files changed, 5 insertions(+), 6 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-24 05:38:14 +0000

[anenadic]

Thank you @amangoel185.