"all types" --> "most types"#153
Conversation
"any type" --> "most types"
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/LibraryCarpentry/lc-git/compare/md-outputs..md-outputs-PR-153 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 2023-10-16 21:08:26 +0000 |
emcaulay
left a comment
There was a problem hiding this comment.
Excellent revision - thank yoU!
Auto-generated via {sandpaper}
Source : 45c8e8a
Branch : md-outputs
Author : GitHub Actions <actions@github.com>
Time : 2023-10-17 19:21:52 +0000
Message : markdown source builds
Auto-generated via {sandpaper}
Source : 0eb4299
Branch : main
Author : Elizabeth McAulay <stassewright@gmail.com>
Time : 2023-10-17 19:20:39 +0000
Message : Merge pull request #153 from ErinBecker/main
"all types" --> "most types"
|
Thanks for the fast review @emcaulay! |
The start of the "What is Git/GitHub" states that "modern version control systems can be used to track changes in any type of file" but later says "Since Word documents contain special formatting, Git unfortunately cannot version control those, nor can it version control PDFs, though both file types can be stored in Git repositories."
This PR changes "any type" to "most types" to avoid contradicting later information.