Open
Conversation
|
@berg Agree with @LewisJEllis makes it easy to view on mobile and also to share |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Someone in a thread asked for PDFs, and I found myself wanting them too; Dalton mentioned that lawyers operate on .docx and thus the canonical source should be .docx, which makes sense, but it seemed easy enough to script some pdf generation and have CI make sure it stays in sync.
Note that the pdf generation is not deterministic / idempotent, as there's some random object id generation + current timestamp metadata stuff going on. I wanted to just do "generate pdfs from inputs, check no git diff, good", but instead had to settle for "generate checksums of inputs, track those, make sure they didn't change". So there's no strong verifiability / provenance here, but it does the job for "I only read PDFs please just let me read a PDF to check it out" type purposes, and if you modify only a .docx then CI will remind you to rebuild the pdfs. Example of the CI check running on my fork here.
I did some exploration of options / approaches and wrote the README, then Claude wrote all the yaml and bash. Feel free to take this and modify / run with it however you like!