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/carpentries-incubator/high-dimensional-stats-r/compare/md-outputs..md-outputs-PR-192 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 2026-03-03 13:41:56 +0000 |
|
Outputs are fine but I want to suppress some of these messages/warnings before merging :) |
|
Two PRs submitted to PCAtools, will wait a few weeks for response |
eb0414c to
c09528e
Compare
c09528e to
fcfc7ca
Compare
fcfc7ca to
ac0532f
Compare
|
PCAtools still broken |
ac0532f to
6b63859
Compare
…nal-stats-r into update/packages
|
Found some errors in there as well... oops! |
…gh-dimensional-stats-r into update/packages
b3cceed to
3d8a1e1
Compare
Auto-generated via `{sandpaper}`
Source : a0c7cbe
Branch : main
Author : The Carpentries Apprentice (beta) <64428345+carpentries-bot@users.noreply.github.com>
Time : 2026-03-03 13:58:50 +0000
Message : Update 51 packages (#192)
* [actions] update 14 packages
* [actions] update 51 packages
* Debug errors
---------
Co-authored-by: alanocallaghan <alanocallaghan@users.noreply.github.com>
Co-authored-by: alanocallaghan <10779688+alanocallaghan@users.noreply.github.com>
Co-authored-by: Alan O'Callaghan <alan.ocallaghan@outlook.com>
Auto-generated via `{sandpaper}`
Source : 445b39f
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-03-03 14:29:19 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : a0c7cbe
Branch : main
Author : The Carpentries Apprentice (beta) <64428345+carpentries-bot@users.noreply.github.com>
Time : 2026-03-03 13:58:50 +0000
Message : Update 51 packages (#192)
* [actions] update 14 packages
* [actions] update 51 packages
* Debug errors
---------
Co-authored-by: alanocallaghan <alanocallaghan@users.noreply.github.com>
Co-authored-by: alanocallaghan <10779688+alanocallaghan@users.noreply.github.com>
Co-authored-by: Alan O'Callaghan <alan.ocallaghan@outlook.com>
Auto-generated via `{sandpaper}`
Source : 445b39f
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2026-03-03 14:29:19 +0000
Message : markdown source builds
Auto-generated via `{sandpaper}`
Source : a0c7cbe
Branch : main
Author : The Carpentries Apprentice (beta) <64428345+carpentries-bot@users.noreply.github.com>
Time : 2026-03-03 13:58:50 +0000
Message : Update 51 packages (#192)
* [actions] update 14 packages
* [actions] update 51 packages
* Debug errors
---------
Co-authored-by: alanocallaghan <alanocallaghan@users.noreply.github.com>
Co-authored-by: alanocallaghan <10779688+alanocallaghan@users.noreply.github.com>
Co-authored-by: Alan O'Callaghan <alan.ocallaghan@outlook.com>
🤖 This is an automated build
This will update 51 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: