<?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: Sanjay Rajpurohit</title>
    <description>The latest articles on DEV Community by Sanjay Rajpurohit (@sanjayrajpurohit356).</description>
    <link>https://dev.to/sanjayrajpurohit356</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fthepracticaldev.s3.amazonaws.com%2Fi%2F99mvlsfu5tfj9m7ku25d.png</url>
      <title>DEV Community: Sanjay Rajpurohit</title>
      <link>https://dev.to/sanjayrajpurohit356</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sanjayrajpurohit356"/>
    <language>en</language>
    <item>
      <title>5 Git Commands I Use Every Day as a Developer</title>
      <dc:creator>Sanjay Rajpurohit</dc:creator>
      <pubDate>Thu, 01 Oct 2026 08:05:13 +0000</pubDate>
      <link>https://dev.to/sanjayrajpurohit356/5-git-commands-i-use-every-day-as-a-developer-43f3</link>
      <guid>https://dev.to/sanjayrajpurohit356/5-git-commands-i-use-every-day-as-a-developer-43f3</guid>
      <description>&lt;p&gt;If you're learning Git, you don't need to memorize 50 commands.&lt;/p&gt;

&lt;p&gt;In my daily development workflow, I mostly use a small set of commands again and again.&lt;/p&gt;

&lt;p&gt;Here are 5 Git commands that every beginner should understand.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. git clone&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When you want to download an existing project from GitHub:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git clone &lt;a href="https://github.com/username/project.git" rel="noopener noreferrer"&gt;https://github.com/username/project.git&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This creates a local copy of the repository on your computer.&lt;/p&gt;

&lt;p&gt;After cloning:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;cd project&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now you can start working on the project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2 git status&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is probably the Git command I use the most.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git status&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It tells you what's happening in your repository.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;modified:   app.js&lt;br&gt;
modified:   styles.css&lt;br&gt;
untracked:  config.js&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Before committing anything, I usually run:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git status&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It helps me see exactly what I've changed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3.git add&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;After making changes, you need to tell Git which files you want to include in your next commit.&lt;/p&gt;

&lt;p&gt;For one file:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git add app.js&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For all changed files:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git add&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Think of git add as:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Git, I want to include these changes."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;4. git commit&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now save those staged changes with a message:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git commit -m "Add login validation"&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A good commit message should briefly explain &lt;strong&gt;what changed&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git commit -m "Fix navbar on mobile"&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;is much more useful than:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git commit -m "changes"&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Small, meaningful commits make your project history much easier to understand.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. git push&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;After committing your changes locally, you can send them to the remote repository:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git push&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Now your changes are available on GitHub or another Git hosting service.&lt;/p&gt;

&lt;p&gt;A simple workflow looks like this:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;git status&lt;br&gt;
git add .&lt;br&gt;
git commit -m "Add new feature"&lt;br&gt;
git push&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;## My simple Git workflow&lt;/p&gt;

&lt;p&gt;Most of the time, my workflow looks something like this:&lt;/p&gt;

&lt;p&gt;Start work&lt;br&gt;
    ↓&lt;br&gt;
git pull&lt;br&gt;
    ↓&lt;br&gt;
Write code&lt;br&gt;
    ↓&lt;br&gt;
git status&lt;br&gt;
    ↓&lt;br&gt;
git add .&lt;br&gt;
    ↓&lt;br&gt;
git commit -m "Describe the change"&lt;br&gt;
    ↓&lt;br&gt;
git push&lt;/p&gt;

&lt;p&gt;You don't need to memorize every Git command to get started.&lt;/p&gt;

&lt;p&gt;Start with these few commands and learn more as you actually need them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Git becomes much easier once you stop trying to memorize it and start using it.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>development</category>
      <category>git</category>
      <category>softwaredevelopment</category>
    </item>
  </channel>
</rss>
