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-lab/deep-learning-intro/compare/md-outputs..md-outputs-PR-626 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-09 14:35:20 +0000 |
Auto-generated via `{sandpaper}`
Source : fa80928
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-01-09 14:42:48 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : c744cdb
Branch : main
Author : Toby Hodges <tobyhodges@carpentries.org>
Time : 2026-01-09 14:41:50 +0000
Message : Merge pull request #626 from carpentries-lab/jose-doi
Add JOSE DOI
Now that the paper has been published in JOSE I think we should use their DOI instead of the Zenodo entry. This PR updates the config file and README accordingly.
Congratulations @carschno and everyone else!