You have commit messages with errors ⧗ input: docs: Correct typo ether→either (#1734) ⚠ scope may not be empty [scope-empty] ⚠ found 0 problems, 1 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: docs(manual): Copy-edit manual and package docs - Spelling/grammar/syntax/usage: - Generally rephrase text to read better and avoid inessential details or noise/slang. - Avoid: of course, obviously, very, and (at start of sentence), so, etc. - Rework some sentences to have fewer semicolons. (An unfortunately common pattern...) - Add some commas between clauses, and remove some others, as needed (Oxford style). - Expand a few terms that may be otherwise unknown to a new user. - Correct spelling errors. - Correct capitalization errors. - According to majority style, only capitalize first word of section & subsection titles. - 'Lua' (not lua or LUA) - Chapter number references (eg, Chapter 4). - Try to be more consistent about using a colon at the end of a sentence that introduces a code block. - In `math`, use direct voice (one may -> you may). - Typography/punctuation: - Use em-dashes consistently (replace --, en-dash, spaces before/after, etc.). - Use quotes consistently (generally double-quotes, not single). - Be consistent about punctuation within quotes, unless clearly indicating a single word, etc. - Try to put footnote references after punctuation, not before. - Use conventional enumerated items within text paragraph. - eg, instead of 1) red, 2) blue -- use (1) red, (2) blue - Remove excessive punctuation (commas, semicolons) from a few itemized lists. - Formatting: - Try to be consistent with itemized lists -- use colon instead of dashes (definition lists would be better in many of these places!). - Avoid hyphenating proper names of software products. - Fix a few code blocks that are wrapping badly or otherwise poorly formatted. - Ensure inline code text is really in \code{} blocks. - Ensure mentions of classes is consistently in \code{} blocks (though probably should use autodoc:class?). - Ensure mentions of values (especially defaults) is consistently in \code{} blocks. - Use \autodoc:parameter{}, etc., in appropriate places (incomplete). - Add a few \noindent's in select places. - Move a couple of references to systems (eg, Fluent) into footnotes. - Correct & simplify SILE bumpy-road examples. - In `linespacing`, use \itemize instead of manual bulleted lists. - Other: - Update/normalize references to products like InDesign, Pages, etc. - Update incorrect URLs. ✖ body's lines must not be longer than 100 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: docs: Update manual for deprecated uses of SILE.registerCommand() ⚠ scope may not be empty [scope-empty] ⚠ found 0 problems, 1 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: fix(typesetter): New typesetter instances shall not reset settings ⚠ scope must be one of [actions, azure, backends, build, cirrus, classes, cli, core, debug, deps, docker, fonts, frames, images, i18n, inputters, installation, languages, api, manpage, manual, math, measurements, nodes, outputters, packages, pagebuilders, pdf, readme, release, rusile, settings, shapers, tooling, types, typesetters, utilities] [scope-enum] ⚠ found 0 problems, 1 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: test(typesetter): Add test for settings after new typesetter instantiation ⚠ scope must be one of [actions, azure, backends, build, cirrus, classes, cli, core, debug, deps, docker, fonts, frames, images, i18n, inputters, installation, languages, api, manpage, manual, math, measurements, nodes, outputters, packages, pagebuilders, pdf, readme, release, rusile, settings, shapers, tooling, types, typesetters, utilities] [scope-enum