docs: scope 80-char hard-wrap to commit messages - #323
Merged
Conversation
The commit-message format section said "hard wrap at 80 characters" with no stated scope, so the rule got applied to GitHub issue and PR bodies too. Those render as GitHub-flavored markdown and soft-wrap on their own; hard wrapping them produces ragged output in the web UI and fights the editor when someone revises the text. State the scope explicitly, matching the equivalent rule in the infra repo's CLAUDE.md. Key changes: - Add a Scope bullet limiting the 80-char hard-wrap to commit messages - Call out that PR descriptions, issues, and comments must not be hard-wrapped, breaking lines only where markdown requires it
ecv
requested review from
0xmc,
JoseSzycho,
aflor024,
drewr,
kevwilliams and
mattdjenkinson
July 28, 2026 17:05
kevwilliams
approved these changes
Jul 28, 2026
1 task
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
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.
Summary
The commit-message format section said "hard wrap at 80 characters" with no stated scope, so the rule got applied to GitHub issue and PR bodies too. Those render as GitHub-flavored markdown and soft-wrap on their own — hard wrapping them produces ragged output in the web UI and fights the editor when someone revises the text.
This states the scope explicitly, matching the equivalent rule already in the infra repo's
CLAUDE.md.Test plan