Skip to content

Conversation

@jonjab
Copy link
Contributor

@jonjab jonjab commented Jun 3, 2025

Reverts #475

That was a change in episode 5 and the lesson build failed.
There was a note about a checkmd file also changing.

I don't see why the 1 word change could prevent the repo from building.

@github-actions
Copy link

github-actions bot commented Jun 3, 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-raster-vector-geospatial/compare/md-outputs..md-outputs-PR-478

The following changes were observed in the rendered markdown documents:

 config.yaml (new) |   92 ++
 renv.lock (new)   | 2747 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 2839 insertions(+)
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-03 19:25:26 +0000

github-actions bot pushed a commit that referenced this pull request Jun 3, 2025
@jonjab jonjab merged commit 0f9b7a7 into main Jun 10, 2025
3 checks passed
@jonjab jonjab deleted the revert-475-patch-2 branch June 10, 2025 18:05
github-actions bot pushed a commit that referenced this pull request Jun 10, 2025
Auto-generated via `{sandpaper}`
Source  : 0f9b7a7
Branch  : main
Author  : Jon Jablonski <jonjab@ucsb.edu>
Time    : 2025-06-10 18:05:27 +0000
Message : Merge pull request #478 from datacarpentry/revert-475-patch-2

Revert "uses consistent carpentries terminology"
github-actions bot pushed a commit that referenced this pull request Jun 10, 2025
Auto-generated via `{sandpaper}`
Source  : c22ca29
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2025-06-10 18:07:45 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 0f9b7a7
Branch  : main
Author  : Jon Jablonski <jonjab@ucsb.edu>
Time    : 2025-06-10 18:05:27 +0000
Message : Merge pull request #478 from datacarpentry/revert-475-patch-2

Revert "uses consistent carpentries terminology"
github-actions bot pushed a commit that referenced this pull request Jun 17, 2025
Auto-generated via `{sandpaper}`
Source  : c22ca29
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2025-06-10 18:07:45 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 0f9b7a7
Branch  : main
Author  : Jon Jablonski <jonjab@ucsb.edu>
Time    : 2025-06-10 18:05:27 +0000
Message : Merge pull request #478 from datacarpentry/revert-475-patch-2

Revert "uses consistent carpentries terminology"
github-actions bot pushed a commit that referenced this pull request Jun 24, 2025
Auto-generated via `{sandpaper}`
Source  : 0f9b7a7
Branch  : main
Author  : Jon Jablonski <jonjab@ucsb.edu>
Time    : 2025-06-10 18:05:27 +0000
Message : Merge pull request #478 from datacarpentry/revert-475-patch-2

Revert "uses consistent carpentries terminology"
github-actions bot pushed a commit that referenced this pull request Jun 24, 2025
Auto-generated via `{sandpaper}`
Source  : 6130610
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2025-06-24 00:38:39 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 0f9b7a7
Branch  : main
Author  : Jon Jablonski <jonjab@ucsb.edu>
Time    : 2025-06-10 18:05:27 +0000
Message : Merge pull request #478 from datacarpentry/revert-475-patch-2

Revert "uses consistent carpentries terminology"
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.

2 participants