<?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: Chukwuamaka Osuji</title>
    <description>The latest articles on DEV Community by Chukwuamaka Osuji (@senseiamaka).</description>
    <link>https://dev.to/senseiamaka</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%2F400082%2F37155ab8-c884-43c4-9553-f0e6a2084dc0.jpeg</url>
      <title>DEV Community: Chukwuamaka Osuji</title>
      <link>https://dev.to/senseiamaka</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/senseiamaka"/>
    <language>en</language>
    <item>
      <title>Cloning a Particular Branch of a Git Repository</title>
      <dc:creator>Chukwuamaka Osuji</dc:creator>
      <pubDate>Tue, 02 Jun 2020 02:41:51 +0000</pubDate>
      <link>https://dev.to/senseiamaka/cloning-a-particular-branch-of-a-git-repository-58k5</link>
      <guid>https://dev.to/senseiamaka/cloning-a-particular-branch-of-a-git-repository-58k5</guid>
      <description>&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--Eadp9p3f--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/w2ffhshbznj1puakc5ey.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--Eadp9p3f--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/w2ffhshbznj1puakc5ey.jpeg" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Using git from the command line is something I have always wished I was good at. When I see how wonderfully well-experienced people use git from the command line, I marvel and am pushed to continue striving to attain an appreciable level of expertise in this art. Thus, whenever I use git, I try as much as possible to do so from the command line, although the lack of consistency has been a problem.&lt;/p&gt;

&lt;p&gt;Recently, I released a second version of the miniature electronic voting application which I developed. Before I committed the codebase for the second version to the GitHub repository, I was not so sure how to go about it because there was a huge difference between the technologies used for the first and the second versions, and as such I could not add the second version as a release, because it required a separate README file. Eventually, I decided to move the first version to a new branch and commit the second and most recent version to the master branch so that I could write separate READMEs for them.&lt;/p&gt;

&lt;p&gt;While drafting the README, I figured that less experienced command line users might find it difficult to clone a specific version (branch) of the app (repository) with the conventional &lt;strong&gt;&lt;em&gt;git clone URL&lt;/em&gt;&lt;/strong&gt; command. After a little research, I discovered a way to do this, which is a little tweak from the conventional command; &lt;code&gt;git clone -b branchname URL&lt;/code&gt; gets the work done. So, if the name of the branch I want to clone is &lt;strong&gt;v1.0&lt;/strong&gt; and the URL to clone the repository is &lt;strong&gt;&lt;a href="https://github.com/Chukwuamaka/ballotpal.git"&gt;https://github.com/Chukwuamaka/ballotpal.git&lt;/a&gt;&lt;/strong&gt;, I would do &lt;code&gt;_git clone -b v1.0 https://github.com/Chukwuamaka/ballotpal.git&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;If you just found out, &lt;strong&gt;welcome to the club!&lt;/strong&gt;&lt;/p&gt;

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