Skip to content

Install packages from CRAN instead of GitHub #180

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

Merged
merged 1 commit into from
May 1, 2025
Merged

Conversation

Bisaloo
Copy link
Member

@Bisaloo Bisaloo commented Apr 24, 2025

No description provided.

@Bisaloo Bisaloo requested a review from avallecam April 24, 2025 14:19
Copy link

github-actions bot commented Apr 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/epiverse-trace/tutorials-middle/compare/md-outputs..md-outputs-PR-180

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                                 |   86 -
 create-forecast.md                                 |   59 +-
 delays-functions.md                                |   14 +-
 ...create-forecast-rendered-unnamed-chunk-10-1.png |  Bin 19262 -> 19287 bytes
 ...create-forecast-rendered-unnamed-chunk-12-1.png |  Bin 18561 -> 18622 bytes
 fig/create-forecast-rendered-unnamed-chunk-4-1.png |  Bin 52637 -> 52893 bytes
 ...elays-functions-rendered-unnamed-chunk-16-1.png |  Bin 54848 -> 54566 bytes
 ...elays-functions-rendered-unnamed-chunk-17-1.png |  Bin 55792 -> 55442 bytes
 ...elays-functions-rendered-unnamed-chunk-20-1.png |  Bin 56377 -> 58103 bytes
 ...elays-functions-rendered-unnamed-chunk-21-1.png |  Bin 34620 -> 34946 bytes
 ...ransmissibility-rendered-unnamed-chunk-10-1.png |  Bin 67407 -> 70234 bytes
 ...ransmissibility-rendered-unnamed-chunk-17-1.png |  Bin 33518 -> 33606 bytes
 ...ransmissibility-rendered-unnamed-chunk-18-1.png |  Bin 38017 -> 38211 bytes
 ...y-static-rendered-unnamed-chunk-20-1.png (gone) |  Bin 26233 -> 0 bytes
 ...ty-static-rendered-unnamed-chunk-9-1.png (gone) |  Bin 21505 -> 0 bytes
 ...estimate-rendered-unnamed-chunk-11-1.png (gone) |  Bin 9104 -> 0 bytes
 ...estimate-rendered-unnamed-chunk-14-1.png (gone) |  Bin 19283 -> 0 bytes
 ...reading-estimate-rendered-unnamed-chunk-4-1.png |  Bin 7209471 -> 6182280 bytes
 md5sum.txt                                         |   20 +-
 network.html                                       |    6 +-
 quantify-transmissibility.md                       |   29 +-
 renv.lock (gone)                                   | 6232 --------------------
 setup.md                                           |   89 +-
 webshot.png                                        |  Bin 7209471 -> 6182280 bytes
 24 files changed, 74 insertions(+), 6461 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-05-01 22:59:10 +0000

github-actions bot pushed a commit that referenced this pull request Apr 24, 2025
Copy link
Member

@avallecam avallecam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @Bisaloo! I agree with these edits.

github-actions bot pushed a commit that referenced this pull request May 1, 2025
@avallecam avallecam merged commit e52f110 into main May 1, 2025
6 checks passed
@avallecam avallecam deleted the github-to-cran branch May 1, 2025 23:14
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