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!
![Welcome to My New Office]()
My first professional web development was at a small print shop where I sat in a windowless cubical all day. I suffered that boxed in environment for almost five years before I was able to find a remote job where I worked from home. The first...
![Create Namespaced Classes with MooTools]()
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
![Unicode CSS Classes]()
CSS class name structure and consistency is really important; some developers camelcase classnames, others use dashes, and others use underscores. One thing I've learned when toying around by HTML and CSS class names is that you can actually use unicode symbols and icons as classnames.
![Create Twitter-Style Dropdowns Using MooTools]()
Twitter does some great stuff with JavaScript. What I really appreciate about what they do is that there aren't any epic JS functionalities -- they're all simple touches. One of those simple touches is the "Login" dropdown on their homepage. I've taken...
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?