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/datacarpentry/organization-geospatial/compare/md-outputs..md-outputs-PR-102 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-04-07 00:28:16 +0000 |
6ebde7b to
3cf39f5
Compare
3cf39f5 to
95e10cc
Compare
95e10cc to
23e7582
Compare
23e7582 to
5db3bcd
Compare
5db3bcd to
f600b06
Compare
f600b06 to
ad3f040
Compare
ad3f040 to
e88d2a5
Compare
e88d2a5 to
aa2e0e0
Compare
aa2e0e0 to
dcc2642
Compare
🤖 This is an automated build
This will update 32 packages in your lesson with the following versions:
⏱️ In a few minutes, a comment will appear that will show you how the output has changed based on these updates.
If you want to inspect these changes locally, you can use the following code to check out a new branch: