# If applied, this commit will...

# Explain why this change is being made

# Provide links to any relevant tickets, articles or other resources


#EXAMPLE OF COMMITT
#Summarize changes in around 50 characters or less

#More detailed explanatory text, if necessary. Wrap it to about 72
#characters or so. In some contexts, the first line is treated as the
#subject of the commit and the rest of the text as the body. The
#blank line separating the summary from the body is critical (unless
#you omit the body entirely); various tools like `log`, `shortlog`
#and `rebase` can get confused if you run the two together.

#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
Create git commit message template
Create git commit message template

# Explain why this change is being made
For better commit messages that will make easier to track history in
future.
# Provide links to any relevant tickets, articles or other resources
Inspiration and help was provided by these articles: [Chris
Beams](http://chris.beams.io/posts/git-commit/) and [David Winterbottom]
(http://codeinthehole.com/writing/a-useful-template-for-commit-
messages/).

#EXAMPLE OF COMMITT
#Summarize changes in around 50 characters or less

#More detailed explanatory text, if necessary. Wrap it to about 72
#characters or so. In some contexts, the first line is treated as the
#subject of the commit and the rest of the text as the body. The
#blank line separating the summary from the body is critical (unless
#you omit the body entirely); various tools like `log`, `shortlog`
#and `rebase` can get confused if you run the two together.

#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
