<?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: Ishimwe Pierre Richard</title>
    <description>The latest articles on DEV Community by Ishimwe Pierre Richard (@ishimwe_ricky).</description>
    <link>https://dev.to/ishimwe_ricky</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%2F1105039%2F0c1f7cc3-87e0-46fc-bce5-618a11b917c4.png</url>
      <title>DEV Community: Ishimwe Pierre Richard</title>
      <link>https://dev.to/ishimwe_ricky</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ishimwe_ricky"/>
    <language>en</language>
    <item>
      <title>Git commits and git branch naming</title>
      <dc:creator>Ishimwe Pierre Richard</dc:creator>
      <pubDate>Tue, 20 Jun 2023 12:18:01 +0000</pubDate>
      <link>https://dev.to/ishimwe_ricky/git-commits-and-git-branch-naming-eo3</link>
      <guid>https://dev.to/ishimwe_ricky/git-commits-and-git-branch-naming-eo3</guid>
      <description>&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--lG-3QRvU--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/hk3alv7ofzu7yg0mfgy6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--lG-3QRvU--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/hk3alv7ofzu7yg0mfgy6.png" alt="Image description" width="800" height="410"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Branches&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Category&lt;/strong&gt;: The first thing to do when naming a branch in git, You have to give it a category. The following are the different categories of git naming.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Feature&lt;/strong&gt;: Used for adding, refactoring, or removing a feature.&lt;br&gt;
&lt;strong&gt;Bugfix&lt;/strong&gt;: Used for fixing a bug.&lt;br&gt;
&lt;strong&gt;Hotfix&lt;/strong&gt;: Used for giving the codes a temporary solution. (Usually because of an emergency).&lt;br&gt;
&lt;strong&gt;Test&lt;/strong&gt;: Used for experimenting outside of a ticket.&lt;br&gt;
&lt;strong&gt;Wip&lt;/strong&gt;: For a work in progress.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reference&lt;/strong&gt;: The second thing to do is to give the branch a reference which begins with a “/” or “-” sign and then the reference. If there is no reference, just add “/no-ref”. &lt;br&gt;
Using separators such as “category/no/ref” or “category-no-ref”, improve the readability, but remember to be consistent with the chosen sign. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;: Depending on the sign you chose to go with between “/” and “-”, after the reference you put another sign, followed by a short description of your message. This description should be “Kebab-cased”, (meaning: a programming variable naming convention, where the space between words and any special character are replaced with a dash “-”). &lt;br&gt;
&lt;strong&gt;Branch naming example:&lt;/strong&gt; &lt;br&gt;
For adding, refactoring, removing a feature use&lt;br&gt;
&lt;strong&gt;git branch feature/issue-10/create-new-button&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For fixing a bug use&lt;br&gt;
&lt;strong&gt;Git branch bugfix/issue-20/signup-button-overlap&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For fixing a bug really fast as a temporary solution use&lt;br&gt;
&lt;strong&gt;Git branch hotfix/issue-30/login-button-not-working&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For experimenting outside of an issue use&lt;br&gt;
&lt;strong&gt;Git branch test/no-ref/refactor-login-component&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--O8CX1WQG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/a6btypufoudstjonz69r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--O8CX1WQG--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/a6btypufoudstjonz69r.png" alt="Image description" width="800" height="400"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Commits&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Category&lt;/strong&gt;: The first thing to do when naming a commit in git, You have to give it a category. The following are the different categories of commit naming.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Feat&lt;/strong&gt;: Used for adding a new feature.&lt;br&gt;
&lt;strong&gt;Fix&lt;/strong&gt;: Used for fixing a bug.&lt;br&gt;
&lt;strong&gt;Refactor&lt;/strong&gt;: Used for changing the codes for performance &lt;br&gt;
&lt;strong&gt;Chore&lt;/strong&gt;: Used for everything else.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Description&lt;/strong&gt;: After the category, the colon sign (:) is written to announce the commit description. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Statement&lt;/strong&gt;: After the colon, a commit description follows in the form of a short statement describing the changes made. Statements are separated by a semi-colon (;).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Commit naming example: **&lt;br&gt;
**Git commit -m”category: added new image; replaced old footer”&lt;/strong&gt;&lt;/p&gt;

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