Skip to content

Conversation

@fnattino
Copy link
Contributor

Closes #178

@fnattino fnattino requested a review from rogerkuou September 11, 2025 19:45
@github-actions
Copy link

github-actions bot commented Sep 11, 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/carpentries-incubator/geospatial-python/compare/md-outputs..md-outputs-PR-179

The following changes were observed in the rendered markdown documents:

 01-intro-raster-data.md |  6 +++---
 03-crs.md               |  2 +-
 04-geo-landscape.md     |  6 ++----
 05-access-data.md       |  2 +-
 06-raster-intro.md      |  2 +-
 08-crop-raster-data.md  |  4 ++--
 12-data-cube.md         | 10 +++++-----
 index.md                |  6 +++---
 md5sum.txt              | 16 ++++++++--------
 9 files changed, 26 insertions(+), 28 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-09-11 19:46:47 +0000

github-actions bot pushed a commit that referenced this pull request Sep 11, 2025
Copy link
Contributor

@rogerkuou rogerkuou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @fnattino, Thanks for the fix! Please go ahead and merge!

@fnattino fnattino merged commit 1b2d095 into main Jan 13, 2026
3 checks passed
@fnattino fnattino deleted the 178-fix-links-fn branch January 13, 2026 11:17
github-actions bot pushed a commit that referenced this pull request Jan 13, 2026
Auto-generated via `{sandpaper}`
Source  : 1b2d095
Branch  : main
Author  : Francesco Nattino <49899980+fnattino@users.noreply.github.com>
Time    : 2026-01-13 11:17:23 +0000
Message : Merge pull request #179 from carpentries-incubator/178-fix-links-fn

Fix links
github-actions bot pushed a commit that referenced this pull request Jan 13, 2026
Auto-generated via `{sandpaper}`
Source  : 8c9bf28
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2026-01-13 13:40:00 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 1b2d095
Branch  : main
Author  : Francesco Nattino <49899980+fnattino@users.noreply.github.com>
Time    : 2026-01-13 11:17:23 +0000
Message : Merge pull request #179 from carpentries-incubator/178-fix-links-fn

Fix links
github-actions bot pushed a commit that referenced this pull request Jan 20, 2026
Auto-generated via `{sandpaper}`
Source  : 8c9bf28
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2026-01-13 13:40:00 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 1b2d095
Branch  : main
Author  : Francesco Nattino <49899980+fnattino@users.noreply.github.com>
Time    : 2026-01-13 11:17:23 +0000
Message : Merge pull request #179 from carpentries-incubator/178-fix-links-fn

Fix links
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.

Broken links

3 participants