-
-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update 16 packages #456
Update 16 packages #456
Conversation
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:
Rendered Changes🔍 Inspect the changes: https://github.com/datacarpentry/r-raster-vector-geospatial/compare/md-outputs..md-outputs-PR-456 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 2024-10-01 00:36:54 +0000 |
f023255
to
073ef51
Compare
073ef51
to
41c2f77
Compare
Auto-generated via `{sandpaper}` Source : 7519729 Branch : md-outputs Author : GitHub Actions <actions@github.com> Time : 2024-10-15 19:19:59 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : aedf804 Branch : main Author : Jon Jablonski <jonjab@ucsb.edu> Time : 2024-10-15 19:12:57 +0000 Message : Merge pull request #456 from datacarpentry/update/packages Update 16 packages
Auto-generated via `{sandpaper}` Source : ba60c97 Branch : md-outputs Author : GitHub Actions <actions@github.com> Time : 2024-10-22 00:26:18 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : aedf804 Branch : main Author : Jon Jablonski <jonjab@ucsb.edu> Time : 2024-10-15 19:12:57 +0000 Message : Merge pull request #456 from datacarpentry/update/packages Update 16 packages
Auto-generated via `{sandpaper}` Source : ba60c97 Branch : md-outputs Author : GitHub Actions <actions@github.com> Time : 2024-10-22 00:26:18 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : aedf804 Branch : main Author : Jon Jablonski <jonjab@ucsb.edu> Time : 2024-10-15 19:12:57 +0000 Message : Merge pull request #456 from datacarpentry/update/packages Update 16 packages
Auto-generated via `{sandpaper}` Source : ba60c97 Branch : md-outputs Author : GitHub Actions <actions@github.com> Time : 2024-10-22 00:26:18 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : aedf804 Branch : main Author : Jon Jablonski <jonjab@ucsb.edu> Time : 2024-10-15 19:12:57 +0000 Message : Merge pull request #456 from datacarpentry/update/packages Update 16 packages
Auto-generated via `{sandpaper}` Source : ba60c97 Branch : md-outputs Author : GitHub Actions <actions@github.com> Time : 2024-10-22 00:26:18 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : aedf804 Branch : main Author : Jon Jablonski <jonjab@ucsb.edu> Time : 2024-10-15 19:12:57 +0000 Message : Merge pull request #456 from datacarpentry/update/packages Update 16 packages
Changes look fine. |
Auto-generated via `{sandpaper}` Source : ba60c97 Branch : md-outputs Author : GitHub Actions <actions@github.com> Time : 2024-10-22 00:26:18 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : aedf804 Branch : main Author : Jon Jablonski <jonjab@ucsb.edu> Time : 2024-10-15 19:12:57 +0000 Message : Merge pull request #456 from datacarpentry/update/packages Update 16 packages
🤖 This is an automated build
This will update 16 packages in your lesson with the following versions:
⏱️ In a few minutes, a comment will appear that will show you how the output has changed based on these updates.
If you want to inspect these changes locally, you can use the following code to check out a new branch: