Skip to content

Commit

Permalink
Commit Message line length is 72 characters (#333)
Browse files Browse the repository at this point in the history
See step 3 in https://docs.typo3.org/m/typo3/guide-contributionworkflow/main/en-us/BugfixingAZ/Index.html#fix-the-code

And also Gerrit code base - CSS:
```css
.commitMessage {
  max-width: calc(72ch + 2px + 2 * var(--spacing-m) + 0.4px);
}
```
  • Loading branch information
rr-it authored Mar 12, 2024
1 parent c9d278e commit 1836d97
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Documentation/Appendix/CommitMessage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ Here is an example of a final commit message. The change-id will be generated by
and not what is has not been working
(that is part of the bug report already).
More detailed explanatory text, if necessary. Wrap it to 74 characters.
More detailed explanatory text, if necessary. Wrap it to 72 characters.
The first line is treated as the subject of the commit message and
the rest of the text as the body. The blank line separating the
subject from the body is critical (unless you omit the body entirely);
Expand All @@ -43,8 +43,8 @@ Here is an example of a final commit message. The change-id will be generated by
The commit message solely describes '''what is changed'''.
* Bullet points are okay, too
* An asterisk (`*`) is used for the bullet, it can be followed by a single
space. This format is rendered correctly by Forge (redmine)
* An asterisk (`*`) is used for the bullet, it can be followed by a
single space. This format is rendered correctly by Forge (redmine)
* Use a hanging indent
Resolves: #12346
Expand Down

0 comments on commit 1836d97

Please sign in to comment.