Skip to content

Conversation

coopermkr
Copy link
Contributor

If this pull request addresses an open issue on the repository, please add 'Closes #NN' below, where NN is the issue number.

Please briefly summarise the changes made in the pull request, and the reason(s) for making these changes.

If any relevant discussions have taken place elsewhere, please provide links to these.

For more guidance on how to contribute changes to a Carpentries project, please review the Contributing Guide and Code of Conduct.

Please keep in mind that lesson Maintainers are volunteers and it may be some time before they can respond to your contribution. Although not all contributions can be incorporated into the lesson materials, we appreciate your time and effort to improve the curriculum. If you have any questions about the lesson maintenance process or would like to volunteer your time as a contribution reviewer, please contact The Carpentries Team at [email protected].

Copy link

github-actions bot commented Jun 24, 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/datacarpentry/r-intro-geospatial/compare/md-outputs..md-outputs-PR-174

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.

⏱️ Updated at 2025-06-24 17:20:49 +0000

github-actions bot pushed a commit that referenced this pull request Jun 24, 2025
@coopermkr coopermkr merged commit d7aa7b0 into main Jun 24, 2025
3 checks passed
@coopermkr coopermkr deleted the coopermkr-patch-1 branch June 24, 2025 17:22
github-actions bot pushed a commit that referenced this pull request Jun 24, 2025
Auto-generated via `{sandpaper}`
Source  : d7aa7b0
Branch  : main
Author  : coopermkr <[email protected]>
Time    : 2025-06-24 17:22:21 +0000
Message : Merge pull request #174 from datacarpentry/coopermkr-patch-1

Added my name to the list of current maintainers. Not going to make someone approve this, I made sure I spelled it right.
github-actions bot pushed a commit that referenced this pull request Jun 24, 2025
Auto-generated via `{sandpaper}`
Source  : a292891
Branch  : md-outputs
Author  : GitHub Actions <[email protected]>
Time    : 2025-06-24 17:24:50 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : d7aa7b0
Branch  : main
Author  : coopermkr <[email protected]>
Time    : 2025-06-24 17:22:21 +0000
Message : Merge pull request #174 from datacarpentry/coopermkr-patch-1

Added my name to the list of current maintainers. Not going to make someone approve this, I made sure I spelled it right.
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