|
|
First, there are people at [Conventional Commits](https://www.conventionalcommits.org) that try to standardize commits and that might be worth a look.
|
|
|
|
|
|
There are other initiatives out there that try to provide guidelines for commit messages such as [these ones from Google](https://gist.github.com/stephenparish/9941e89d80e2bc58a153).
|
|
|
|
|
|
# Git commit message prefixes
|
|
|
|
|
|
* [RFR] - Code refectoring
|
|
|
* [WIP] - Work in progress
|
|
|
* [FIX] - Bug fix
|
|
|
* [FTR] - New feature
|
|
|
* [SCR] - Security issue fix
|
|
|
* [CLP] - Changes that do not alter functionality, but improve code style and readability.
|
|
|
* [CRO] - Content Rate Optimization
|
|
|
* [TST] - Add test suite for slider component
|
|
|
* [!!!] - Deprecated. Can only be used with `[FTR]`
|
|
|
|
|
|
# Lima Domain commit message prefixes
|
|
|
|
|
|
* [CMAKE] Anything related to the build system
|
|
|
* [LIMA.RPC] RPC framework
|
|
|
* [LIMA.PROC] Processing framework
|
|
|
* [LIMA.xxx] You name it |
|
|
\ No newline at end of file |