Skip to main content

Command Palette

Search for a command to run...

Git for Beginners: Basics and Essential Commands

Published
4 min read

Git is like Ctrl + Z for your whole project—but better.When you’re coding (or writing anything), Git lets you save checkpoints.Made a mess? Just go back to the last good version.

  • Git = the tool on your computer

  • GitHub = where you store your project online (like Google Drive for code)

What is Git

Git is a version control system.

In simple words:

Git helps you track changes in your code over time.

Instead of saving files like:

Git keeps everything clean and organized.

It remembers:

  • What changed

  • Who changed it

  • When it changed

Extra knowledge:
Git was created by Linus Torvalds, the same person who created Linux.

Why Git is Used

Git is used because software projects:

  • Change often

  • Are worked on by many people

  • Need backup and history

Git helps developers:

  • Go back to older versions

  • Work together safely

  • Fix mistakes without fear

Without Git, managing code becomes messy very fast.

Extra knowledge:
Most companies will not accept a project if it is not managed using Git.

Git as a Distributed Version Control System

Git is distributed, not centralized.

This means:

  • Every developer has a full copy of the project

  • Work can be done even without internet

  • No single point of failure

Each developer’s machine is powerful on its own.

Extra knowledge:
Even if the central server crashes, the project can be recovered from any developer’s system.

Git Basics and Core Terminologies

Let’s understand the most important Git terms.

Repository (Repo)

A repository is a folder where Git tracks changes.

It contains:

  • Project files

  • Git history

  • Configuration

Commit

A commit is a saved snapshot of your work.

It represents:

“This is what my code looks like right now.”

Branch

A branch is a separate line of work.

You can:

  • Experiment safely

  • Add new features

  • Fix bugs without breaking main code

HEAD

HEAD points to:

  • Your current position in Git history

  • The latest commit you are working on

Extra knowledge:
Think of HEAD as a bookmark that tells Git where you currently are.

Initializing a Git Repository

To start using Git in a project, use:

git init

This command:

  • Turns a normal folder into a Git repository

  • Creates a hidden .git folder

  • Starts version tracking

Now Git is watching your project.

Extra knowledge:
Deleting the .git folder removes Git completely from the project.

Checking File Status with Git

To see what Git is tracking, use:

git status

This command shows:

  • Modified files

  • New files

  • Files ready to be committed

It is the most used Git command.

Extra knowledge:
Developers run git status many times a day to stay safe.

Adding Files to Git

To tell Git which changes to save, use:

git add .

This command:

  • Stages all changes

  • Prepares them for commit

Git does not save changes automatically.
You must tell Git what to track.

Extra knowledge:
Staging exists so you can control exactly what goes into a commit.

Saving Changes with Git Commit

To save changes permanently, use:

git commit -m "message"

A commit:

  • Stores your changes

  • Requires a message explaining what you did

Good commit messages make projects easy to understand.

Extra knowledge:
A commit without a clear message is considered bad practice.

Viewing History with Git Log

To see all past commits, use:

git log

This shows:

  • Commit history

  • Author

  • Date

  • Commit message

It is like a timeline of your project.

Extra knowledge:
Git history helps developers find when and where bugs were introduced.

Basic Developer Workflow Using Git

A simple Git workflow looks like this:

  1. Create or modify files

  2. Check status

     git status
    
  3. Add changes

     git add .
    
  4. Commit changes

     git commit -m "message"
    

Repeat this cycle while working.

This flow builds discipline and safety.

Extra knowledge:
Small and frequent commits are better than one big commit.

Common Beginner Mistakes in Git

Beginners often:

  • Forget to commit

  • Write unclear commit messages

  • Panic when mistakes happen

  • Avoid branches

Git is designed to handle mistakes, not punish them.

Extra knowledge:
Almost every Git mistake can be fixed if you understand the basics.

Summary For Fast Understanding

Git is not just a tool.
It is a way of thinking about code changes.

Git helps you:

  • Track progress

  • Collaborate confidently

  • Build professional projects

If cURL teaches you how to talk to servers,
Git teaches you how to manage your code properly.

Extra knowledge:
Learning Git early makes learning GitHub, GitLab, and DevOps much easier.