Skip to content

Commit bd92658

Browse files
authored
doc: add no-line-wrapping convention for commit messages (#13742)
1 parent 3757160 commit bd92658

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

.claude/CLAUDE.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -104,12 +104,13 @@ Subject should use imperative present tense ("add" not "added"), no capitalizati
104104

105105
**Body format:** The first paragraph must start with "This PR". This paragraph is automatically incorporated into release notes, so keep it short, focus on user-side impact, and avoid implementation-specific wording. Save the implementation details for a follow-up paragraph. Use imperative present tense. Do NOT use markdown headings (`## Summary`, `## Test plan`, etc.) in PR bodies.
106106

107+
**Line wrapping:** Do NOT hard-wrap lines in commit messages or PR descriptions. Write each paragraph as a single line and let display tools (GitHub, `git log`, terminals) soft-wrap. Bullet lists are still fine; just keep each `* item` body on one line.
108+
107109
Example:
108110
```
109111
feat: add optional binder limit to `mkPatternFromTheorem`
110112
111-
This PR adds a `num?` parameter to `mkPatternFromTheorem` to control how many
112-
leading quantifiers are stripped when creating a pattern.
113+
This PR adds a `num?` parameter to `mkPatternFromTheorem` to control how many leading quantifiers are stripped when creating a pattern.
113114
```
114115

115116
**Changelog labels:** Add one `changelog-*` label to categorize the PR for release notes:

0 commit comments

Comments
 (0)