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

clarify code block that is not run and break out nano steps #1061

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

erinmgraham
Copy link
Contributor

Closes #891

Code blocks with 'bash' that are not can be confusing and this lesson often uses nano and cat in the same code block without the bit in the middle. It is definitely more time consuming to separate but I think also easier for beginners to follow.

Copy link

github-actions bot commented Jan 10, 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/swcarpentry/git-novice/compare/md-outputs..md-outputs-PR-1061

The following changes were observed in the rendered markdown documents:

 04-changes.md |  6 +++---
 06-ignore.md  | 14 ++++++++++++++
 md5sum.txt    |  4 ++--
 3 files changed, 19 insertions(+), 5 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-01-10 06:37:31 +0000

github-actions bot pushed a commit that referenced this pull request Jan 10, 2025
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.

Recommended comments to clarify sections
1 participant