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

[code readability episode] adding narratives #50

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

sgibson91
Copy link
Contributor

No description provided.

Copy link

github-actions bot commented May 10, 2024

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/fair-research-software/compare/md-outputs..md-outputs-PR-50

The following changes were observed in the rendered markdown documents:

 04-code-readability.md | 141 ++++++++++++++++++++++++++++++++++++++++++++++---
 md5sum.txt             |   2 +-
 2 files changed, 134 insertions(+), 9 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 2024-05-29 10:41:05 +0000

github-actions bot pushed a commit that referenced this pull request May 10, 2024
- why is clear naming of variables important
- useful tips for naming variables
- common gotchas (mostly for python) when naming variables
github-actions bot pushed a commit that referenced this pull request May 10, 2024
github-actions bot pushed a commit that referenced this pull request May 20, 2024
github-actions bot pushed a commit that referenced this pull request May 22, 2024
github-actions bot pushed a commit that referenced this pull request May 24, 2024
github-actions bot pushed a commit that referenced this pull request May 29, 2024
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.

None yet

1 participant