scatterd-dotfiles/gitmessage



# 50-character subject line
#
# 72-character wrapped longer description. This should answer:
#
# * Why was this change necessary?
# * How does it address the problem?
# * Are there any side effects?
#
# Include a link to the ticket, if any.
Add a commit message template Using the `commit.template` setting, read in a commit message template for each commit. This template is commented out so the commit message author doesn't need to delete it. The template serves as a reminder on how to write a better commit message. The bullets are taken from Caleb's blog post[1]. There is no _problem_ per se -- we are writing good messages these days -- but it's handy to be reminded of things to think about. For example, people often forget to note whether there are any side effects. This message does not show on `git commit --amend`, only normal `git commit`. [1] http://bit.ly/13HWyiy 2013-09-12 10:30:48 +02:00

			`# 50-character subject line`
Remove trailing whitespace in gitmessage 2014-04-18 16:24:37 -04:00			`#`
Add a commit message template Using the `commit.template` setting, read in a commit message template for each commit. This template is commented out so the commit message author doesn't need to delete it. The template serves as a reminder on how to write a better commit message. The bullets are taken from Caleb's blog post[1]. There is no _problem_ per se -- we are writing good messages these days -- but it's handy to be reminded of things to think about. For example, people often forget to note whether there are any side effects. This message does not show on `git commit --amend`, only normal `git commit`. [1] http://bit.ly/13HWyiy 2013-09-12 10:30:48 +02:00			`# 72-character wrapped longer description. This should answer:`
Remove trailing whitespace in gitmessage 2014-04-18 16:24:37 -04:00			`#`
Add a commit message template Using the `commit.template` setting, read in a commit message template for each commit. This template is commented out so the commit message author doesn't need to delete it. The template serves as a reminder on how to write a better commit message. The bullets are taken from Caleb's blog post[1]. There is no _problem_ per se -- we are writing good messages these days -- but it's handy to be reminded of things to think about. For example, people often forget to note whether there are any side effects. This message does not show on `git commit --amend`, only normal `git commit`. [1] http://bit.ly/13HWyiy 2013-09-12 10:30:48 +02:00			`# * Why was this change necessary?`
			`# * How does it address the problem?`
			`# * Are there any side effects?`
Remove trailing whitespace in gitmessage 2014-04-18 16:24:37 -04:00			`#`
Add a commit message template Using the `commit.template` setting, read in a commit message template for each commit. This template is commented out so the commit message author doesn't need to delete it. The template serves as a reminder on how to write a better commit message. The bullets are taken from Caleb's blog post[1]. There is no _problem_ per se -- we are writing good messages these days -- but it's handy to be reminded of things to think about. For example, people often forget to note whether there are any side effects. This message does not show on `git commit --amend`, only normal `git commit`. [1] http://bit.ly/13HWyiy 2013-09-12 10:30:48 +02:00			`# Include a link to the ticket, if any.`