chore(committed): increase subject length to 72 #1532
Merged
+1
−0
Conversation
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
50 is a tad too short, 72 reaps benefits well enough. 72 is what we had with gitlint, too.
yedayak
approved these changes
Dec 30, 2025
akinomyoga
approved these changes
Dec 30, 2025
Collaborator
|
Thanks! |
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.
50 is a tad too short, 72 reaps benefits well enough. 72 is what we had with gitlint, too.
Note that we'll still have 72 for commit body lines (I think we used to have 80). 72 is a better default for that, as it keeps the message display tidy on 80-char terminal, taking git log indentation into account.