traduccion

[Joskerus]

No description provided.

[github-actions]

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/Joskerus/EpiTKit-EN/compare/md-outputs..md-outputs-PR-1

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                                 |   88 -
 estadistica.md                                     | 1672 ++++---
 ...adistica-rendered-unnamed-chunk-12-1.png (gone) |  Bin 19201 -> 0 bytes
 ...adistica-rendered-unnamed-chunk-15-1.png (gone) |  Bin 5283 -> 0 bytes
 ...adistica-rendered-unnamed-chunk-25-1.png (gone) |  Bin 9479 -> 0 bytes
 ...adistica-rendered-unnamed-chunk-26-1.png (gone) |  Bin 4496 -> 0 bytes
 ...tadistica-rendered-unnamed-chunk-3-1.png (gone) |  Bin 12047 -> 0 bytes
 ...tadistica-rendered-unnamed-chunk-4-1.png (gone) |  Bin 12038 -> 0 bytes
 ...tadistica-rendered-unnamed-chunk-5-1.png (gone) |  Bin 3102 -> 0 bytes
 ...tadistica-rendered-unnamed-chunk-8-1.png (gone) |  Bin 7559 -> 0 bytes
 md5sum.txt                                         |   34 +-
 renv.lock (gone)                                   | 5091 --------------------
 12 files changed, 830 insertions(+), 6055 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-06-06 17:14:53 +0000