Git Comment Convention

Comment structure

First line is a subject line. It should have size about 50 characters, maximum limit is 80. Subject line is capitalized and hasn't period at the end;
A blank line separates subject from body;
Detailed description of the change in the body, breaking paragraphs where needed. The body should explain what you did and why vs. how. The body also starts with a capitalized letter. Bullet points are made with an asterisk (*);
In case if a bug tracking system is used, bug Id's line is placed at the very end after a blank line.

[FEATURE]: A new feature (also small additions). Most likely it will be an added feature, but it could also be removed;
[BUGFIX]: A fix for a bug;
[STYLE]: Changes in layout, page style and css files;
[CLEANUP]: Code formatting, improvements in code style and readability;
[DOCS]: Changes to documentation;
[TEST]: Adding, changing, refactoring tests - no production code change;
[OTHER]: Anything not covered by the above categories.

(!!!) : Breaking change. Significant changes in software architecture or logic, that affect existing features and extentions or change user experience;
(DB): Changes that require database structure or data to be updated;
(WIP): Work in progress. This flag will be removed, once the final version of a change is available. Changes marked WIP are never merged.

(!!!)(DB)[FEATURE] Rewrite stored procedure

Additional information about commit changes