github-actions[bot]
commented
7 months 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:
- :dart: correct output
- :framed_picture: correct figures
- :question: new warnings
- :bangbang: new errors
Rendered Changes
:mag: Inspect the changes: https://github.com/carpentries-incubator/geospatial-python/compare/md-outputs..md-outputs-PR-171
The following changes were observed in the rendered markdown documents:
md5sum.txt | 2 +-
setup.md | 22 ++++++++++++++++++++--
2 files changed, 21 insertions(+), 3 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.:stopwatch: Updated at 2024-04-30 17:04:39 +0000
As an alternative to jumping into the command line for setting up and launching the geospatial virtual environment, this addition explains how the Anaconda Navigator can be used for the entire process.