Skip to content

recover epitkit from varnish#4

Merged
avallecam merged 1 commit intomainfrom
avallecam-patch-1
Jun 20, 2025
Merged

recover epitkit from varnish#4
avallecam merged 1 commit intomainfrom
avallecam-patch-1

Conversation

@avallecam
Copy link
Member

  • Please check if the PR fulfills these requirements
  • I have read the CONTRIBUTING guidelines
  • A new item has been added to NEWS.md
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • Checks have been run locally and pass
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

  • What is the current behavior? (You can also link to an open issue here)

  • What is the new behavior (if this is a feature change)?

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

  • Other information:

@github-actions
Copy link

github-actions bot commented Jun 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/epimodelac-en/compare/md-outputs..md-outputs-PR-4

The following changes were observed in the rendered markdown documents:

 config.yaml | 2 +-
 md5sum.txt  | 2 +-
 2 files changed, 2 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-06-20 09:36:05 +0000

github-actions bot pushed a commit that referenced this pull request Jun 20, 2025
@avallecam avallecam merged commit c7b0ffb into main Jun 20, 2025
3 checks passed
@avallecam avallecam deleted the avallecam-patch-1 branch June 26, 2025 16:11
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.

1 participant