<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ishan Makadia</title>
    <description>The latest articles on DEV Community by Ishan Makadia (@ishanmakadia).</description>
    <link>https://dev.to/ishanmakadia</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F422697%2F0a4ad47b-d452-40cf-af58-52a25da058b6.PNG</url>
      <title>DEV Community: Ishan Makadia</title>
      <link>https://dev.to/ishanmakadia</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ishanmakadia"/>
    <language>en</language>
    <item>
      <title>Git commit message convention that you can follow!</title>
      <dc:creator>Ishan Makadia</dc:creator>
      <pubDate>Sun, 21 Mar 2021 07:37:38 +0000</pubDate>
      <link>https://dev.to/ishanmakadia/git-commit-message-convention-that-you-can-follow-1709</link>
      <guid>https://dev.to/ishanmakadia/git-commit-message-convention-that-you-can-follow-1709</guid>
      <description>&lt;p&gt;Motivation of this blog is to curate all information at one place and to make more people aware about standards followed by industry.&lt;/p&gt;

&lt;p&gt;Let's get started.....&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;A typical git commit message will look like&lt;br&gt;
&lt;/p&gt;
&lt;/blockquote&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;&amp;lt;type&amp;gt;(&amp;lt;scope&amp;gt;): &amp;lt;subject&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  "type" must be one of the following mentioned below!
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;build&lt;/code&gt;: Build related changes (eg: npm related/ adding external dependencies) &lt;/li&gt;
&lt;li&gt;
&lt;code&gt;chore&lt;/code&gt;: A code change that external user won't see (eg: change to .gitignore file or .prettierrc file)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;feat&lt;/code&gt;: A new feature&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;fix&lt;/code&gt;: A bug fix&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;docs&lt;/code&gt;: Documentation related changes&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;refactor&lt;/code&gt;: A code that neither fix bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;perf&lt;/code&gt;: A code that improves performance&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;style&lt;/code&gt;: A code that is related to styling&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;test&lt;/code&gt;: Adding new test or making changes to existing test&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  "scope" is optional
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Scope must be noun and it represents the section of the section of the codebase&lt;/li&gt;
&lt;li&gt;
&lt;a href="http://karma-runner.github.io/1.0/dev/git-commit-msg.html"&gt;Refer this link for example related to scope&lt;/a&gt; &lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  "subject"
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;use imperative, present tense (eg: use "add" instead of "added" or "adds")&lt;/li&gt;
&lt;li&gt;don't use dot(.) at end&lt;/li&gt;
&lt;li&gt;don't capitalize first letter&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://github.com/eslint/eslint/commits/master"&gt;Refer this link for more practical examples of commit messages&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  References:
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.conventionalcommits.org/en/v1.0.0/"&gt;https://www.conventionalcommits.org/en/v1.0.0/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716"&gt;https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/fteem/git-semantic-commits"&gt;https://github.com/fteem/git-semantic-commits&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>github</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>git</category>
    </item>
  </channel>
</rss>
