search

UoMResearchIT / docker-introduction

An introduction to Docker in the style of the Software Carpentries
https://uomresearchit.github.io/docker-introduction/
Other
0 stars 0 forks source link

Spucsvi welcome message #62

Closed fherreazcue closed 1 month ago

fherreazcue commented 1 month ago

I was getting a print per worker... couldn't fix it, so went for using a single worker... feel free to fix and merge if you can think of another way...

github-actions[bot] commented 1 month ago

Thank you!

Thank you for your pull request :smiley:

:robot: 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

:mag: Inspect the changes: https://github.com/UoMResearchIT/docker-introduction/compare/md-outputs..md-outputs-PR-62

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.

:stopwatch: Updated at 2024-10-21 19:35:17 +0000

OliverWoolland commented 1 month ago

Hmm well it's not a true production deployment so single worker probably fine!

Personally I kinda like the prints per worker...