.git_commit_message.txt

# Summarize changes in around 50 characters or less, no '.' at the end

# Blank line separation from Subject line.
# More detailed explanatory text, if necessary.
# Wrap it to about 72 characters or so.

# Explain the problem that this commit is solving. Focus on why you
# are making this change as opposed to how (the code explains that).
# Are there side effects or other unintuitive consequences of this
# change? Here's the place to explain them.

#Further paragraphs come after blank lines.
#
# - Bullet points are okay, too
#
# - Typically a hyphen or asterisk is used for the bullet, preceded
#   by a single space, with blank lines in between, but conventions
#   vary here

#If you use an issue tracker, put references to them at the bottom,
#like this:
#
# Resolves: #123
# See also: #456, #789

# See http://chris.beams.io/posts/git-commit/