(add git commit message.template) |
No edit summary |
||
| Line 103: | Line 103: | ||
==Good and Consistent commit messages== | ==Good and Consistent commit messages== | ||
You hopefully know what constitutes a [https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html | You hopefully know what constitutes a [https://cbea.ms/git-commit/ good] [https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html commit message]. What about consistency? Say you need to add standard language to every commit message like | ||
<tt>"This work was performed for NASA GRC-ATF by WikiWorks per NASA Contract NNC15BA02B."</tt> | <tt>"This work was performed for NASA GRC-ATF by WikiWorks per NASA Contract NNC15BA02B."</tt> | ||
To consistently format your commit messages, use the configuration parameter <code>commit.template</code> which you can do with <code>git config</code>, or else in your ~/.gitconfig file. | To consistently format your commit messages, use the configuration parameter <code>commit.template</code> which you can do with <code>git config</code>, or else in your ~/.gitconfig file. Here's my [[Git/commit.template|commit.template]] | ||
https://thoughtbot.com/blog/5-useful-tips-for-a-better-commit-message | https://thoughtbot.com/blog/5-useful-tips-for-a-better-commit-message | ||
| Line 320: | Line 320: | ||
<br /> | <br /> | ||
== Rewriting History == | ==Rewriting History== | ||
Developers need git as a way to track changes and collaborate on software. Release Engineers need git, and '''higher-level''' tools to manage entire repositories of code. Whether Developer or Release Engineer, sometimes you need a do over. | Developers need git as a way to track changes and collaborate on software. Release Engineers need git, and '''higher-level''' tools to manage entire repositories of code. Whether Developer or Release Engineer, sometimes you need a do over. | ||
edits
