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/LibraryCarpentry/lc-python-intro/compare/md-outputs..md-outputs-PR-183 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-09-25 22:24:17 +0000 |
|
Looks great overall! Just one comment above. |
Auto-generated via `{sandpaper}`
Source : 13b7479
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-09-29 19:49:19 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : 8b69203
Branch : main
Author : Cody Hennesy <codyhennesy@gmail.com>
Time : 2026-09-29 19:47:41 +0000
Message : Merge pull request #183 from LibraryCarpentry/audience
clarify scope to emphasize circulation dataset
Closes #180
Clarify the learner profiles and audience for the lesson by noting that the dataset and exercises focus on library circulation data, though the Python skills are relevant in other library use cases.