<story><title>Commit messages are not titles</title><url>http://antirez.com/news/90</url></story><parent_chain><item><author>stared</author><text>Dots, periods or starting with caps - it makes no difference (except for aesthetics, perhaps.) What does (or at least: did for me) is Angular-style commit messages: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;angular&amp;#x2F;angular.js&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;CONTRIBUTING.md#commit&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;angular&amp;#x2F;angular.js&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;CONTRIBUTI...&lt;/a&gt;.&lt;p&gt;&amp;gt; &amp;lt;type&amp;gt;(&amp;lt;scope&amp;gt;): &amp;lt;subject&amp;gt;&lt;p&gt;&amp;gt; [...]&lt;p&gt;&amp;gt; feat: A new feature&lt;p&gt;&amp;gt; fix: A bug fix&lt;p&gt;&amp;gt; docs: Documentation only changes&lt;p&gt;&amp;gt; style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)&lt;p&gt;&amp;gt; refactor: A code change that neither fixes a bug or adds a feature&lt;p&gt;&amp;gt; perf: A code change that improves performance&lt;p&gt;&amp;gt; test: Adding missing tests&lt;p&gt;&amp;gt; chore: Changes to the build process or auxiliary tools and libraries such as documentation generation&lt;p&gt;There is a big difference in knowing if someone added a feature, fixed something, or did some refactoring.</text></item></parent_chain><comment><author>braythwayt</author><text>Whenever I see a convention like this, I think to myself, “There is another data model being serialized into text.”</text></comment>
<story><title>Commit messages are not titles</title><url>http://antirez.com/news/90</url></story><parent_chain><item><author>stared</author><text>Dots, periods or starting with caps - it makes no difference (except for aesthetics, perhaps.) What does (or at least: did for me) is Angular-style commit messages: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;angular&amp;#x2F;angular.js&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;CONTRIBUTING.md#commit&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;angular&amp;#x2F;angular.js&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;CONTRIBUTI...&lt;/a&gt;.&lt;p&gt;&amp;gt; &amp;lt;type&amp;gt;(&amp;lt;scope&amp;gt;): &amp;lt;subject&amp;gt;&lt;p&gt;&amp;gt; [...]&lt;p&gt;&amp;gt; feat: A new feature&lt;p&gt;&amp;gt; fix: A bug fix&lt;p&gt;&amp;gt; docs: Documentation only changes&lt;p&gt;&amp;gt; style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)&lt;p&gt;&amp;gt; refactor: A code change that neither fixes a bug or adds a feature&lt;p&gt;&amp;gt; perf: A code change that improves performance&lt;p&gt;&amp;gt; test: Adding missing tests&lt;p&gt;&amp;gt; chore: Changes to the build process or auxiliary tools and libraries such as documentation generation&lt;p&gt;There is a big difference in knowing if someone added a feature, fixed something, or did some refactoring.</text></item></parent_chain><comment><author>arethuza</author><text>For some reason the fact that &amp;quot;feature&amp;quot; is abbreviated to &amp;quot;feat&amp;quot; while &amp;quot;refactor&amp;quot; which is actually longer than &amp;quot;feature&amp;quot; is left alone irritates me - which, of course, doesn&amp;#x27;t mean anything other than to demonstrate how silly this kind of argument can be!</text></comment>