1. 16
  1. 5

    I never liked the omission of the full stop at the end of the so called summary, and started adding it many years ago. There are others with similar experience. Let me link to antirez’s blog post to avoid explaining it myself: http://antirez.com/news/90

    1. 1

      Worth noting that the commit messages produced by git (like for merge commits) do not add a period (by default).

      1. 1

        I often edit merge commits, and when I do I obviously add lacking period.

      2. 1

        Thanks for the link, I’ll be saving it!

      3. 1

        Good advice. I would add, though, that when working with a defect-tracking system, write the summary to reference the defect and defect summary:

        Defect #: Defect Summary.

        Or whatever format the system requires to link the commit to the defect. (s/defect/feature/g as needed)

        1. 1

          I actually read somewhere (probably from a long forgotten link shared here) to avoid being imperative in my commit messages!

          1. 1

            Perhaps add “(2008)” to the title of this post?

            Stories with similar links:

            1. A Note About Git Commit Messages (2008) via wezm 3 months ago | 17 points | no comments