Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Preventing SourceTree from splitting up commit message?

thomthom September 29, 2013

Have a look at this commit I made for a GitHub repo:

https://github.com/thomthom/SKUI/commit/17d6b9f17d6ab358c29b793059c82300554a12f1

The title I entered was:

Ensuring that checking and unchecking methods of the Checkbox control work. Fixing #61.

But somewhere along the lines that got broken in two parts and the trailing part ended up in the description. This looks odd and it also prevented the issue from being automatically closed.

Is there a way to prevent SourceTree from splitting up the commit message?

1 answer

1 accepted

1 vote
Answer accepted
KieranA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 29, 2013

Hi Thomas,

This isn't anything to do with SourceTree. GitHub take a certain amount of characters/words and use that as the title. Anything beyond that is treated as part of the message. It's just the way they format commit messages. Take for example this: https://github.com/kieransenior/jquery-treetable/commit/980bdd3ab61d54c850ada6746aadeaa4967d7277. Same thing happens (not my commit). You can search throughout GitHub and see the same thing happening.

Cheers

thomthom September 29, 2013

Oh, I was so sure I'd used longer commit messages than that. Maybe that was BitBucket then. My bad.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events