Skip to content
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

Adapting slides for session 1 #73

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alwil
Copy link
Collaborator

@alwil alwil commented Feb 3, 2025

I have made changes to the slides for session 1.

@cforgaci, I don't know if we should update slides each time we make a workshop or just keep this on fork
@javisanmillan, please have a look at slides and let me know if you would like to adapt something.

Copy link

github-actions bot commented Feb 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/carpentries-incubator/r-geospatial-urban/compare/md-outputs..md-outputs-PR-73

The following changes were observed in the rendered markdown documents:

 1-Intro-to-R-slides.html            | 414 ++++++++++++++++++++++++++++--------
 18-import-and-visualise-osm-data.md |   4 +-
 fig/ggplot2_masterpiece.png (new)   | Bin 0 -> 1590886 bytes
 fig/here.png (new)                  | Bin 0 -> 3742192 bytes
 4 files changed, 323 insertions(+), 95 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-02-03 17:17:58 +0000

github-actions bot pushed a commit that referenced this pull request Feb 3, 2025
@cforgaci
Copy link
Collaborator

cforgaci commented Feb 3, 2025

I have made changes to the slides for session 1.

Thanks! I will have a look sometime before the workshop. You can still rehearse and present from your fork.

@cforgaci, I don't know if we should update slides each time we make a workshop or just keep this on fork

Indeed, we might want to keep only a template slide deck in the incubator repo and keep our slides in forks. In the long term, we will work with forks of the consolidated repo and we can keep edition-specific slides there. Let's discuss this after the workshop.

@javisanmillan, please have a look at slides and let me know if you would like to adapt something.

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