Docs: Update git message template

.gitlab/.gitmessage

 # Title: Summary, imperative, start upper case, don't end with a period
+# Follow the formatting of <type>:<description>
 # No more than 50 chars. #### 50 chars is here:  #
 
+# Types: Fix, Feat, Build, CI, Docs, Perf, Refactor, Style, Test
+# See: https://www.conventionalcommits.org/en/v1.0.0/
 # Remember blank line between title and body.
 
 # Body: Explain *what* and *why* (not *how*). Include task ID (Jira issue).
 # Wrap at 72 chars. ################################## which is here:  #
 
 
-# At the end: Include Co-authored-by for all contributors. 
-# Include at least one empty line before it. Format: 
-# Co-authored-by: name <user@users.noreply.github.com>
-#
+# Tell Git to use this template with: git config commit.template .gitlab/.gitmessage
 # How to Write a Git Commit Message:
-# https://chris.beams.io/posts/git-commit/
-#
-# 1. Separate subject from body with a blank line
-# 2. Limit the subject line to 50 characters
-# 3. Capitalize the subject line
-# 4. Do not end the subject line with a period
-# 5. Use the imperative mood in the subject line
-# 6. Wrap the body at 72 characters
-# 7. Use the body to explain what and why vs. how
\ No newline at end of file
+# https://chris.beams.io/posts/git-commit/
\ No newline at end of file