WesleyGoncalves · February 20, 2020 00:01 · WesleyGoncalves · Jun 12, 2019
diff --git a/.git-commit-template b/.git-commit-template
 # <type>[(optional scope)]: (If applied, this commit will...) <subject> (Max 50 char)
 # |<----  Using a Maximum Of 50 Characters  ---->|


 # Explain why this change is being made
 # |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|


 # Provide links or keys to any relevant tickets, articles or other resources
 # Example: Github issue #23

 # --- COMMIT END ---
 # Type can be 
 #    feat     (new feature)
 #    fix      (bug fix)
 #    refactor (refactoring production code)
 #    style    (formatting, missing semi colons, etc; no code change)
 #    deprecate (a special case of documentation. You should use it when some resource/code *become deprecated* - added so changelog generators can create a section for these changes as suggested by https://keepachangelog.com/en/1.0.0/#how) 
 #    remove   (a special case of documentation. You should use it when some (deprecated or not) resource/code *is removed*  - added so changelog generators can create a section for these changes as suggested by https://keepachangelog.com/en/1.0.0/#how) 
 #    docs     (changes to documentation)
 #    test     (adding or refactoring tests; no production code change)
 #    chore    (updating grunt tasks etc; no production code change)
 # --------------------
 # Remember to
 #    Capitalize the subject line
 #    Use the imperative mood in the subject line
 #    Do not end the subject line with a period
 #    Separate subject from body with a blank line
 #    Separate body from footer with a blank line
 #    Use the body to explain what and why vs. how
 #    Can use multiple lines with(out) "-" in body
 # --------------------
 # For more information about this template, check out
 # https://gist.github.com/WesleyGoncalves/c4d6799f26931e478e1b74a05c7f0a5a
 # and the Conventional Commits in https://www.conventionalcommits.org/
	# <type>[(optional scope)]: (If applied, this commit will...) <subject> (Max 50 char)
	# \|<---- Using a Maximum Of 50 Characters ---->\|


	# Explain why this change is being made
	# \|<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->\|


	# Provide links or keys to any relevant tickets, articles or other resources
	# Example: Github issue #23

	# --- COMMIT END ---
	# Type can be
	# feat (new feature)
	# fix (bug fix)
	# refactor (refactoring production code)
	# style (formatting, missing semi colons, etc; no code change)
	# deprecate (a special case of documentation. You should use it when some resource/code become deprecated - added so changelog generators can create a section for these changes as suggested by https://keepachangelog.com/en/1.0.0/#how)
	# remove (a special case of documentation. You should use it when some (deprecated or not) resource/code is removed - added so changelog generators can create a section for these changes as suggested by https://keepachangelog.com/en/1.0.0/#how)
	# docs (changes to documentation)
	# test (adding or refactoring tests; no production code change)
	# chore (updating grunt tasks etc; no production code change)
	# --------------------
	# Remember to
	# Capitalize the subject line
	# Use the imperative mood in the subject line
	# Do not end the subject line with a period
	# Separate subject from body with a blank line
	# Separate body from footer with a blank line
	# Use the body to explain what and why vs. how
	# Can use multiple lines with(out) "-" in body
	# --------------------
	# For more information about this template, check out
	# https://gist.github.com/WesleyGoncalves/c4d6799f26931e478e1b74a05c7f0a5a
	# and the Conventional Commits in https://www.conventionalcommits.org/