Skip to content

Conversation

@avallecam
Copy link
Member

  • Please check if the PR fulfills these requirements
  • I have read the CONTRIBUTING guidelines
  • Checks have been run locally and pass

@github-actions
Copy link

github-actions bot commented Oct 20, 2025

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:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/epiverse-trace/tutorials-middle/compare/md-outputs..md-outputs-PR-246

The following changes were observed in the rendered markdown documents:

 md5sum.txt         | 2 +-
 severity-static.md | 8 +++++++-
 2 files changed, 8 insertions(+), 2 deletions(-)
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 2025-10-20 15:51:18 +0000

github-actions bot pushed a commit that referenced this pull request Oct 20, 2025
github-actions bot pushed a commit that referenced this pull request Oct 20, 2025
@avallecam avallecam merged commit 78fbe21 into main Oct 20, 2025
6 checks passed
@avallecam avallecam deleted the cfr-prepare-data-fix-i2 branch October 20, 2025 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants