Skip to content

Creating a pre lesson#106

Draft
skeating wants to merge 8 commits into
mainfrom
sk/create_r_function_links
Draft

Creating a pre lesson#106
skeating wants to merge 8 commits into
mainfrom
sk/create_r_function_links

Conversation

@skeating
Copy link
Copy Markdown
Contributor

No description provided.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 25, 2026

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/SAFEHR-data/omop-carpentries/compare/md-outputs..md-outputs-PR-106

The following changes were observed in the rendered markdown documents:

 001_intro.md (new)                        | 241 ++++++++++++++++++++++++++++++
 01_what_is_omop.md                        |   2 +-
 02_exploring_omop_concepts.md             |  16 +-
 03_parquet_files.md                       |  15 +-
 04_other_concepts.md                      |  33 ++--
 06_conditions_visits.md                   |  11 +-
 basic-r-functions-used.md (new)           |   8 +
 data/omop/visit_occurrence/part-0.parquet | Bin 3885 -> 5004 bytes
 fig/person_ehr.png (new)                  | Bin 0 -> 142747 bytes
 md5sum.txt                                |  40 ++---
 workshop.zip                              | Bin 301610 -> 297510 bytes
 11 files changed, 307 insertions(+), 59 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 2026-04-29 10:35:49 +0000

github-actions Bot pushed a commit that referenced this pull request Apr 29, 2026
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