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

rearrange content and callouts #27

Merged
merged 1 commit into from
Dec 14, 2023
Merged

rearrange content and callouts #27

merged 1 commit into from
Dec 14, 2023

Conversation

avallecam
Copy link
Member

  • Please check if the PR fulfills these requirements
  • I have read the CONTRIBUTING guidelines
  • A new item has been added to NEWS.md
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

introduction rearrangement

Copy link

github-actions bot commented Dec 14, 2023

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/research-compendium/compare/md-outputs..md-outputs-PR-27

The following changes were observed in the rendered markdown documents:

 introduction.md | 37 +++++++++++++++++++------------------
 md5sum.txt      |  2 +-
 2 files changed, 20 insertions(+), 19 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 2023-12-14 18:06:08 +0000

github-actions bot pushed a commit that referenced this pull request Dec 14, 2023
@avallecam avallecam merged commit 070687d into main Dec 14, 2023
3 checks passed
@avallecam avallecam deleted the rearrange-intro branch December 14, 2023 18:09
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