ph-One · June 8, 2022 13:27
diff --git a/.gitmessage b/.gitmessage
 # git config --global commit.template ~/.gitmessage
 # https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines
 #
 # <subject> and <body>:
 # - use the imperative, present tense: "change" not "changed" nor "changes". 
 # - no capitalization of first letter
 # - no punctuation
 #
 # If applied this change will <subject>
 <type>(<scope>): <subject>
 # BLANK LINE
 <body>
 # BLANK LINE
 <footer>
 #
 # The <scope> can be anything specifying place of the commit change.
 #
 # <type>
 # feat: A new feature
 # fix: A bug fix
 # docs: Documentation only changes
 # style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 # refactor: A code change that neither fixes a bug nor adds a feature
 # perf: A code change that improves performance
 # test: Adding missing or correcting existing tests
 # chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
 #
 # Revert
 # If the commit reverts a previous commit, it should begin with revert: , followed by the header of 
 # the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is the 
 # SHA of the commit being reverted.
 #
 # <footer>
 # The footer contains any information about Breaking Changes and also 
 # is where you can reference any Github issues that are closed by this commit.
	# git config --global commit.template ~/.gitmessage
	# https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines
	#
	# <subject> and <body>:
	# - use the imperative, present tense: "change" not "changed" nor "changes".
	# - no capitalization of first letter
	# - no punctuation
	#
	# If applied this change will <subject>
	<type>(<scope>): <subject>
	# BLANK LINE
	<body>
	# BLANK LINE
	<footer>
	#
	# The <scope> can be anything specifying place of the commit change.
	#
	# <type>
	# feat: A new feature
	# fix: A bug fix
	# docs: Documentation only changes
	# style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
	# refactor: A code change that neither fixes a bug nor adds a feature
	# perf: A code change that improves performance
	# test: Adding missing or correcting existing tests
	# chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
	#
	# Revert
	# If the commit reverts a previous commit, it should begin with revert: , followed by the header of
	# the reverted commit. In the body it should say: This reverts commit <hash>., where the hash is the
	# SHA of the commit being reverted.
	#
	# <footer>
	# The footer contains any information about Breaking Changes and also
	# is where you can reference any Github issues that are closed by this commit.