How to Set a Default Commit Message
Having a default commit message is really useful for a number of reasons:
- It can formalize your commit messages
- It serves as a good reminder for the information you should add to your commit message, like issue number
- If you set it to "Drunk AF, don't accept this"
To set a default commit message on your local machine, start by executing the following from command line:
git config --global commit.template ~/.gitmessage
This tells your local git config to pull the text from ~/.gitmessage as the default commit message. You could set the text to something like:
Fix Issue #{number}: {description}
R+: {reviewer}
Of course, if you set your commit message via git commit -m {description}, the default will not be used, so it's a win-win!
![5 HTML5 APIs You Didn’t Know Existed]()
When you say or read "HTML5", you half expect exotic dancers and unicorns to walk into the room to the tune of "I'm Sexy and I Know It." Can you blame us though? We watched the fundamental APIs stagnate for so long that a basic feature...
![Create a CSS Flipping Animation]()
CSS animations are a lot of fun; the beauty of them is that through many simple properties, you can create anything from an elegant fade in to a WTF-Pixar-would-be-proud effect. One CSS effect somewhere in between is the CSS flip effect, whereby there's...
![Add Site Screenshots for External Links Using MooTools Tooltips]()
Before you send your user to an unknown external website, why not provide them a screenshot of the site via a tooltip so they may preview the upcoming page? Here's how you can do just that using MooTools.
The MooTools JavaScript
The first step is to grab...
![Reverse Element Order with CSS Flexbox]()
CSS is becoming more and more powerful these days, almost to the point where the order of HTML elements output to the page no longer matters from a display standpoint -- CSS lets you do so much that almost any layout, large or small, is possible. Semantics...
What if you want to include some of the lines from the default commit message in your template? One thing that is not indicated here is that the content of the default message is included with your template content (combined) when the actual commit template is displayed in the editor.
See: commit.template section in https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration
Or test it yourself..
BUT! What if you need to change the order that the default commit message lines appear in your templated commit message? For example..
The default git commit message (as of this date) is:
=======================================================================
# Please enter the commit message for your changes. Lines starting
# with ‘#’ will be ignored, and an empty message aborts the commit.
#
# On branch master
#
# Initial commit
#
# Changes to be committed:
# new file: blah
#
# ———————— >8 ————————
# Do not modify or remove the line above.
# Everything below it will be ignored.
diff –git a/blah b/blah
new file mode 100644
index 0000000..e69de29
=======================================================================
But what if you need it to be:
=======================================================================
Changes to be committed: new file: blah
On branch master
Initial commit
# ———————— >8 ————————
# Do not modify or remove the line above.
# Everything below it will be ignored.
diff –git a/blah b/blah
new file mode 100644
index 0000000..e69de29
=======================================================================
Where “Initial commit” is included / omitted (as it normally is) based on whether it is the initial commit or not. In other words, you want to reformat the default commit message’ content so that when it is combined with your template it will read in the order and format that you want it.
Is there a way to do this?