Skip to content

Update 03-working-with-MARC-files.md#211

Merged
jenmawe merged 3 commits intomainfrom
abigailsparling-patch-14
Apr 10, 2026
Merged

Update 03-working-with-MARC-files.md#211
jenmawe merged 3 commits intomainfrom
abigailsparling-patch-14

Conversation

@abigailsparling
Copy link
Copy Markdown
Contributor

Partial Update. Will continue to add to this PR

Partial Update. Will continue to add.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 27, 2026

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/LibraryCarpentry/lc-marcedit/compare/md-outputs..md-outputs-PR-211

The following changes were observed in the rendered markdown documents:

 03-working-with-MARC-files.md | 23 +++++++++++------------
 md5sum.txt                    |  4 ++--
 reference.md                  |  3 +++
 3 files changed, 16 insertions(+), 14 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 2026-04-09 22:16:20 +0000

github-actions Bot pushed a commit that referenced this pull request Mar 27, 2026
github-actions Bot pushed a commit that referenced this pull request Apr 9, 2026
@abigailsparling abigailsparling marked this pull request as ready for review April 9, 2026 22:19
@abigailsparling
Copy link
Copy Markdown
Contributor Author

Closes #203 Do we need/want to link from the lesson to the glossary for my new Character Encoding entry? It doesn't look like we've done that for the rest of the lesson.

@jenmawe
Copy link
Copy Markdown
Contributor

jenmawe commented Apr 10, 2026

That is a good idea @abigailsparling

@jenmawe jenmawe merged commit 477cf06 into main Apr 10, 2026
5 checks passed
github-actions Bot pushed a commit that referenced this pull request Apr 10, 2026
Auto-generated via `{sandpaper}`
Source  : 477cf06
Branch  : main
Author  : jenmawe <jenmawe@gmail.com>
Time    : 2026-04-10 14:03:18 +0000
Message : Merge pull request #211 from LibraryCarpentry/abigailsparling-patch-14

Update 03-working-with-MARC-files.md
github-actions Bot pushed a commit that referenced this pull request Apr 10, 2026
Auto-generated via `{sandpaper}`
Source  : fa54a80
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2026-04-10 14:05:08 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 477cf06
Branch  : main
Author  : jenmawe <jenmawe@gmail.com>
Time    : 2026-04-10 14:03:18 +0000
Message : Merge pull request #211 from LibraryCarpentry/abigailsparling-patch-14

Update 03-working-with-MARC-files.md
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.

2 participants