Istill remember the first time I heard the word “Git.”
We were in the middle of working on an academic project during our first year, and everyone around me kept mentioning GitHub, repositories, commits, and version control. Honestly, I had no idea what any of those words meant at the time.

After coming home, I searched for the word “Git,” hoping for a simple explanation.
The first thing that appeared everywhere was the term Version Control.

At first, that sounded even more confusing.

Why would developers need something called version control?
Why was Git so important in software development?
And what exactly was the difference between Git and GitHub?

If you are someone who has asked these same questions, this article is for you.

In this beginner-friendly guide, I’ll explain:

• What Git is
• What GitHub is
• What repositories are
• Common GitHub terms beginners should know
• And why developers use Git in real-world projects

Let’s get started.

What is Git?

Imagine you are writing a long essay for university. You keep saving copies of it as you go “essay1”, “essayfinal”, “essayFINALfinal”… sound familiar right?

Now imagine doing that with hundreds of code files, across a team of ten developers, all working on the same project at the same time.

That is the problem Git solves.

Git is a version control system. It tracks every change you make to your code over time. With Git, you can:

• Go back to any previous version of your code
• See exactly what changed, when, and who changed it
• Work on the same project with other developers without overwriting each other’s work.

What is GitHub?

If Git is the tool, GitHub is the place where you store and share your work.

GitHub is a website that hosts your Git projects online. Think of it like Google Drive — but specifically built for code. Once your code is on GitHub, you can:

• Access it from any device
• Share it with teammates or the public
• Let others contribute to your project
• Show your work to future employers

Here is a simple way to remember the difference:

What is a Repository?

A repository (or “repo” for short) is simply a folder that Git is tracking.

When you create a new project and initialize Git inside it, that folder becomes a repository. Everything inside it — your code files, images, config files — is tracked by Git.

Repositories can be

• Local — stored on your computer
• Remote — stored on a platform like GitHub

When you push your local repo to GitHub, you now have both a local copy and a remote copy. This is one of the most powerful things about Git — your code is never in just one place.

Commit

Explain:

• Saving changes with a message
• Like creating checkpoints

Push

Explain:

• Uploading local changes to GitHub

Pull

Explain:

• Downloading latest changes from GitHub

Clone

Explain:

• Copying a repository to your computer

Branch

Explain:

• Separate version of a project for testing features

Merge

Explain:

• Combining branches together

Fork

Explain:

• Copying someone else’s repository into your account

Pull Request (PR)

Explain:

• Requesting changes to be reviewed before merging

README File

Explain:

• Introduction/documentation file of the project

Why Developers Use Git in Real Projects?

At this point you might be thinking, "Okay, I understand what Git is ; but do I actually need it?”

The answer is yes, and here is why.

Every company uses it. Whether it is a startup or a large tech company, Git is the industry standard for managing code. Knowing Git is not optional; it is expected.

It prevents disasters. Without version control, one bad change can break everything, and there is no way to undo it. With Git, you can always roll back to a previous working version.

It enables teamwork. Multiple developers can work on different parts of the same project at the same time, on separate branches, without stepping on each other’s work.

Your GitHub profile is your portfolio. Recruiters and hiring managers look at GitHub profiles to see what candidates have built. Every repo you create and every commit you make contribute to your public profile.

A Simple First Workflow

Here is what a basic Git and GitHub workflow looks like for a beginner:

1. Create a new repository on GitHub
2. Clone it to your computer: git clone <repo-url>
3. Make changes to your files
4. Stage your changes: git add .
5. Commit with a message: git commit -m “my first commit”
6. Push to GitHub: git push

That is it. Those six steps are the foundation of everything.

When I first encountered Git, I felt completely lost — not because it is complicated, but because no one explained it in plain language.

Once you understand the core concepts — what a repo is, what a commit does, and the difference between Git and GitHub — everything else starts to make sense.

You do not need to memorise every command on day one. Start by creating a repository, making a few commits, and pushing your code to GitHub. The rest will come naturally with practice.

If this article helped you, share it with someone who is just getting started. We were all beginners once.

Written by a fellow beginner, for beginners.