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-514 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 2026-01-27 13:42:17 +0000 |
douglowe
left a comment
There was a problem hiding this comment.
This looks good to me.
I have made one comment about adding a note about the CITATION.cff file being our single point of truth - but I don't know if we need this here, so dismiss the comment if you disagree.
|
|
||
| Contributors of more significant changes to the lesson may be invited by the Maintainers to add themselves to the | ||
| Authors list. | ||
| Contributors of more significant changes to the lesson may be invited by the Maintainers to add themselves to the Authors list and CITATION.cff. |
There was a problem hiding this comment.
Should we add a note here that the CITATION.cff file is our source of truth for authors?
Fixes #506.