Repository navigation
docs(vale): accept the spec-hash and supply-chain terms - #2018
Conversation
Spec 20 (spec-hash epoch 1) uses these words as defined terms: codec, injective, injectivity, keyspace, preimage, biconditional, encodable, varint, Sigstore and pkgs. Vale's spelling rule flags each of them.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 3 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 4 reviews per hour. 📝 WalkthroughWalkthroughThe Minimal vocabulary list adds 13 entries: ChangesMinimal vocabulary additions
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~4 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This change adds accepted terms for Spec 20; no concrete user-facing or operational risk is identified, so it is mergeable subject to normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit checks the word list with care, Comment |
|
Approved: no findings at Nothing to do. Clobber: none: |
Summary
Adds 13 words to the Vale vocabulary (
styles/config/vocabularies/Minimal/accept.txt):biconditional,codec,codecs,encodable,injective,injectivity,keyspace,pkgs,preimage,preimages,Sigstore,varint,varints. Spec 20 (spec-hash epoch 1, #1305) uses them as defined terms, andVale.Spellingflags each one. Inserted in the file's existing order.Testing
.vale.iniondocs/specs/20-spec-spec-hash-epoch1/20-spec-spec-hash-epoch1.md(docs(specs): spec-hash epoch 1, an injective, machine-checked BuildSpec encoding #1305's head plus this change): no spelling alerts on any of the 13 words; the remaining spelling alerts are test identifiers.just lint-prosewith no arguments fails on main before and after this change, ondocs/specs/TEMPLATE.md's frontmatter (<feature name>is not valid YAML). That is separate from this change.Checklist
BREAKING CHANGE:footer present if this is a breaking changeSummary by CodeRabbit