SourceTree comments in commit message (starting with '#')

When using commit.template config (see SourceTree reads the template file just fine. When committing, it doesn't ignore lines starting with '#' though, as it was designed by git.

In the terminal, when committing with a message that contains lines starting with a '#', git ignores those lines and does not make them part of the actual commit message. SourceTree on the other hand makes them part of the actual commit message.

Is this behaviour wanted? If yes, why?

I want commit message templates that explain where what goes, specifying keywords that dynamically interact with a project management platform (Redmine, as comments that should be ignored in the actual commit message.

I'm currently working with SourceTree on Windows 8 and system Git version 1.9.0


2 answers

1 accepted

4 votes
Answer accepted

It is possible to configure the commit cleanup mode.

If you configure "commit.cleanup" to "strip", SourceTree will behave more as you would like ( "as it was designed by git" smile )


git config --add commit.cleanup strip

Perfect! Thanks

And the reason can be found in the documentation for the commit.cleanup option:


Strip leading and trailing empty lines, trailing whitespace, commentary and collapse consecutive empty lines.


Same as strip except #commentary is not removed.



Same as strip if the message is to be edited. Otherwise whitespace.


The crucial part is "is to be edited" in the description of the default setting.

When committing from the command line and letting Git open an editor the mode used will be "strip". But if you supply the commit message using "-m" or "-F" the "whitespace" mode will be used.

By looking at "Show Full Output" when committing from SourceTree you can see that the commit message is saved to a temporary file and supplied to Git using the "-F" option.

Same problem here.

Mac OSX Yosemite, SourceTree: Version (

System Git version 2.3.0

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 9 hours ago in Agile

Managing Projects in Several Jiras at the Same Time

Have you ever noticed that fixing specific problems might be a door opener for a bigger challenge, affecting a wider audience? This was exactly the case when we, as a service company working with mul...

56 views 0 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you