Allow commit message to be overridden by git config. #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks like a useful compromise. I'm going to merge it, assuming it survives testing on a few of my machines. |
simonthum
added a commit
that referenced
this pull request
Jul 1, 2014
Allow commit message to be overridden by git config.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As suggested in #3. This does not allow the commit message to be evaluated and means the default message is evaluated at beginning of script so in theory the date could be a second or two before the actually commit, but seems better than loads of escaping and weirdness.
I will be using this fork for some projects of mine where I want a static message.
Thoughts?