Fix wording around Git working directory#453
Conversation
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:
Rendered Changes🔍 Inspect the changes: https://github.com/carpentries-incubator/python-intermediate-development/compare/md-outputs..md-outputs-PR-453 The following changes were observed in the rendered markdown documents: 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-06-19 08:22:23 +0000 |
|
@amangoel185 has fixed the diagram - waiting for it to be added to the PR and then we can merge |
amangoel185
left a comment
There was a problem hiding this comment.
Looks good - have added the new SVG!
|
Great stuff @amangoel185 - merging this PR. |
Auto-generated via `{sandpaper}`
Source : 804149d
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2025-06-19 08:44:04 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 7c1c8cf
Branch : main
Author : Aleksandra Nenadic <a.nenadic@manchester.ac.uk>
Time : 2025-06-19 08:43:22 +0000
Message : Merge pull request #453 from carpentries-incubator/anenadic-issues-242
Fix wording around Git working directory
Not sure why my new svg diagram is not looking ok on GitHub - looks OK. Needs checking locally by a reviewer.