The Documentation Team currently does not have strict “rules” for commit messages. These are recommendations.
Commit Message Recommendations¶
- Write commit messages that are clear, concise and meaningful
- Use imperative form: “Fix typo” (instead of “Fixed typo”). This is seen from the person, that is going to apply your patch: What will the patch do? Fix typo!
- As in the TYPO3 core commit message rules, try to keep first line below 52 characters if possible, but below 80 in any case.
- A commit message for the docs should consists of a subject line (first line). More lines (seperated by first line with an empty new line) are optional.
- If an issue exists, link to it, by using “Resolves: #issue number”, e.g. “Resolves: #4”.
- If it should be backported to an older branch, use
Releases:(as in commitmessage)
Example Commit Message With Issue¶
Add chapter for commit message rules Resolves: #4
This consists of the following parts:
<subject> Resolves: #<issue number>
The issue number is optional. GitHub will automatically create a link to the issue.
If you are editing online with GitHub, this may look like this:
Using “Resolves”, will automatically close the issue. You can use “Related” instead of “Resolves” if you do not want the issue to be closed.
You can refer to more than one issue:
<subject> Resolves: #<issue number> Resolves: #<issue number>
Add the branches to which the change should be added:
<subject> Resolves: #<issue number> Releases: master, 9.5
Using TYPO3 Core Commit Message Rules¶
If you wish, you can use the prefixes [BUGFIX],[FEATURE],[TASK] etc. as is customary in core development (see commitmessage).
However, this is not mandatory throughout the docs at the moment. If possible, use the conventions, that are being used in the manual in which you are working, e.g. TYPO3 Explained commits typically use these conventions.