1. Exquisite Tweets from @s1mn, @dannybull, @nickcharlton, @abitgone, @hugovk, @mdales, @brighty

    hugovkCollected by hugovk

    I am horribly inconsistent in the tense of my commit messages. "Fixed foo", "Fixes foo", "Fixing foo", "Fix foo" all common. Shame.

    Reply Retweet Like

    s1mn

    Simon Whitaker

  2. Missing tweet: 177334359035097089

  3. @s1mn Ditto. We need an industry standard for commit messages.

    Reply Retweet Like

    dannybull

    Danny Bull

  4. Missing tweet: 177334839161270272

  5. @s1mn Because you'll always be looking at them in the past tense, that's the one to use.

    Reply Retweet Like

    abitgone

    Anthony Williams

  6. Missing tweet: 177335947619352576

  7. @s1mn StackExchange favours past tense: bit.ly/zgkjcs bit.ly/Aql3W5 but Git recommends imperative present (for DVCS patches).

    Reply Retweet Like

    hugovk

    @hugovk@mastodon.social

  8. Missing tweet: 177336181728620544

  9. Missing tweet: 177336643915751425

  10. So far: two votes for past tense ("Fixed a bug"), two for present imperative ("Fix a bug").

    Reply Retweet Like

    s1mn

    Simon Whitaker

  11. @pigonwheels Inspired an idea - worstcommitmessagesever.com - crowd sourced from public repos cc @s1mn

    Reply Retweet Like

    dannybull

    Danny Bull

  12. 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.

    Reply Retweet Like

    s1mn

    Simon Whitaker

  13. @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

    Reply Retweet Like

    mdales

    Michael Dales

  14. @brighty I don't think it matters much which style you choose, it's my inconsistency that bugs me. It's messy.

    Reply Retweet Like

    s1mn

    Simon Whitaker

  15. Protected tweet: 177342018803077120
    You might be able to see it if you sign in with Twitter.

  16. @osteslag Nice tip, thanks. (I use codebasehq.com, works similarly there - you add [new_status: ticket_id] to commit msg.)

    Reply Retweet Like

    s1mn

    Simon Whitaker

  17. Protected tweet: 177344381324500992
    You might be able to see it if you sign in with Twitter.