I am horribly inconsistent in the tense of my commit messages. "Fixed foo", "Fixes foo", "Fixing foo", "Fix foo" all common. Shame.
10:04am Mar 7th 2012 via Osfoora for Mac
@s1mn Ditto. We need an industry standard for commit messages.
10:07am Mar 7th 2012 via TweetDeck in reply to s1mn
@s1mn I aim to follow this: tbaggery.com/2008/04/19/a-n…
I do, most of the time.
10:09am Mar 7th 2012 via Twitterrific for Mac in reply to s1mn
@s1mn Because you'll always be looking at them in the past tense, that's the one to use.
10:10am Mar 7th 2012 via Twitter for Mac in reply to s1mn
@s1mn StackExchange favours past tense: bit.ly/zgkjcs bit.ly/Aql3W5 but Git recommends imperative present (for DVCS patches).
10:13am Mar 7th 2012 via TweetDeck in reply to s1mn
So far: two votes for past tense ("Fixed a bug"), two for present imperative ("Fix a bug").
10:15am Mar 7th 2012 via Osfoora for Mac
@pigonwheels Inspired an idea - worstcommitmessagesever.com - crowd sourced from public repos cc @s1mn
10:17am Mar 7th 2012 via TweetDeck
I think I have a natural pref for present imperative but use commit messages as basis for release notes where past tense makes more sense.
10:20am Mar 7th 2012 via Osfoora for Mac
@s1mn I've never worried about it, and just stick to a single profane word per commit. Forces you to be creative towards the end of projects
10:26am Mar 7th 2012 via Twitter for Mac in reply to s1mn
@s1mn does it really matter?
10:19am Mar 7th 2012 via Twitter for iPad in reply to s1mn
Mrs Big Bad O'Teddy
@brighty I don't think it matters much which style you choose, it's my inconsistency that bugs me. It's messy.
10:33am Mar 7th 2012 via Osfoora for Mac in reply to brighty
@osteslag Nice tip, thanks. (I use codebasehq.com, works similarly there - you add [new_status: ticket_id] to commit msg.)
10:49am Mar 7th 2012 via Osfoora for Mac in reply to osteslag
Connect with Twitter
A website by @jwheare