peterkc/.git-commit-template.txt

## .git-commit-template.txt
# (<type>): <subject>

# <body>

# <footer>


# <type> should be one of the following:
#
# Fix - for a bug fix.
# Update - for a backwards-compatible enhancement.
# Breaking - for a backwards-incompatible enhancement.
# Docs - changes to documentation only.
# Build - changes to build process only.
# New - implemented a new feature.
# Upgrade - for a dependency upgrade.

# Scope is just the scope of the change. Something like (admin) or (teacher).
# Subject should use impertivite tone and say what you did.
# Body should go into detail about changes made.
# Footer should contain any JIRA (or other tool) issue references or actions (ABC-123, ABC-456).

# For a full example of how to write a good commit message, check out
# http://confluence.zephyr-intranet.com/pages/viewpage.action?title=GIT+commit+message+conventions&spaceKey=EN
	# (<type>): <subject>

	# <body>

	# <footer>


	# <type> should be one of the following:
	#
	# Fix - for a bug fix.
	# Update - for a backwards-compatible enhancement.
	# Breaking - for a backwards-incompatible enhancement.
	# Docs - changes to documentation only.
	# Build - changes to build process only.
	# New - implemented a new feature.
	# Upgrade - for a dependency upgrade.

	# Scope is just the scope of the change. Something like (admin) or (teacher).
	# Subject should use impertivite tone and say what you did.
	# Body should go into detail about changes made.
	# Footer should contain any JIRA (or other tool) issue references or actions (ABC-123, ABC-456).

	# For a full example of how to write a good commit message, check out
	# http://confluence.zephyr-intranet.com/pages/viewpage.action?title=GIT+commit+message+conventions&spaceKey=EN