Conversation
with edits from @sstevens2 and @katrinabrock
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/better-research-software-r/compare/md-outputs..md-outputs-PR-38 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-02-03 15:52:19 +0000 |
with edits from @sstevens2 and @katrinabrock
Recreated from #23
Discussed in 2026-02-03 meeting. Issues with rebasing and permissions to push to @jsgro's repo. Decided to make this PR to supersede #23. Sorry for the anti git way of doing things.
Will clean up a couple of last suggestions from #23 and then get merged. Issues that we find with this episode can get their own issues and PRs filed from here on out.
closes #6