# Git Basics and Essential Commands for Beginners

![Cover image for Git Basics and Essential Commands for Beginners](https://prod-files-secure.s3.us-west-2.amazonaws.com/1daf8d7b-bd6a-4278-9213-f77aa4198ce5/ed925e6d-7e63-42bc-8cba-220384960271/7886fa4c-5324-47fb-a2d9-40bd74e43739.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=ASIAZI2LB466UNGDYV4B%2F20261101%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20261101T133316Z&X-Amz-Expires=3600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEJr%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMiJHMEUCICo6CiitQCF1hOp0HGhXbEe13WxKTEgJdccyIaCRyS4mAiEAyRcdy3xDQM7tE17I4WfbWpGFl2DXEggcxsWAD3cxzqMq%2FwMIYhAAGgw2Mzc0MjMxODM4MDUiDMNUivakXt%2FFK27kpyrcA%2FYdFe0ioPcaC9JYkQSuwS8xIGblgkvxDGYn2NLy8pNveGFxWSP%2BOKjfqzvoRsM61OXBz8BMrs7javVngE475gCgEEdIovaOIUVe7dV%2Fy4r6jjhF1CkCezn4%2ByB8bsEIyLa6IY5AOe61jYFUlvjXFxmZlHeanmtiLBw4SbASTqW8oIReGlD24e6nPN6AeUhg92SJg9cdUK2w%2FgKL8pvKI8obfRd4y3xcgSg%2BfSZl2qXrXKzhfW%2BF1mrLBy2uV9b7pXo3GMP%2B4wXYcR39S9thJm1Inlka5EVLlVyOMegO3eXfZ%2BlKoy0PQXcW1RWpd%2F37MA8sR2XY2dzfvkjtwW%2Ba5jL7uk%2FVUceNIpx2fiMMIJuVhSo%2F0hRdfjEEalJss%2Bpqbl0Ufr1nngN5Djr6lfd861O%2FQFwwB6NdXXK1CWNp1rpQ7am%2BY%2BjVeKn4VBDkBTzJllFsbhAssDoFTarru1V9e%2FKNue9745APad1GuBtFEst7jRPjsd0arur3AiFwS3jtL390bb%2BTvR1TjnyUGGEz2F2OIO0okLL9IvQ%2F%2FuLH88M4phcbMdltHavos7JsbGL8QKNXHssWATMxbBCnVXRat7FIsl722NBZKZHsDZLn%2F%2BqsJE2lXYAdHgegEd62MJeSnNcGOqUBW8Ue%2BcchD%2BpgRMSJF7ncfw8dqlTpk8C%2FrPKZwsI3nlK%2FhJ5Ytau%2BTPQrNNNyTP85LWc1RQ5P3cF7iTY%2BhwZnBCIB9EVyDN2R%2Fs0DI%2Bjv2%2BDGfnVR0Cx%2Bb7AIMwLMVBGrFRQbIqiBAudK%2F%2F2d%2Bi%2Bke%2BUY%2BVI%2FI5MuA115WWnyuW8ntrffUrLnEkYHpB82dTRCjlTuv0Sk5X69hFf9nfGeHkWmWnM%2B&X-Amz-Signature=2cf39743b466c4eb78c55d49a441a10355961bc4ffe9ba396801b234e9e9ae06&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

## No More “Final_Final_v2.js”: A Beginner's Guide to Git

If you’ve ever found yourself with a folder full of files named project.code, project_final.code, and project_final_REAL.code, you already know why you need Git. We’ve all been there. But there is a better way.

## What is Git? (In Simple Terms)

Technically, Git is a Distributed Version Control System (VCS). That sounds intimidating, so let's break it down:

Think of Git as a Time Machine for your code. It keeps a perfect record of every change you make. If you mess something up, you can simply "rewind" to a point when everything was working perfectly.

### Why do we use it?

- Collaboration: Multiple people can work on the same project without overwriting each other's work.

- Snapshots: Unlike "Saving" (which overwrites the old version), Git saves "Snapshots" of your project over time.

- Experimentation: You can try new ideas without risking your main, working code.

---

## Core Concepts: The Vocabulary

Before we type any commands, we need to learn the lingo:

1. Repository (Repo): This is just the folder where your project lives. It’s where Git tracks your files.

1. Commit: This is a "save point." When you commit, you are taking a snapshot of your project at that exact moment.

1. Branch: Imagine an alternate reality. You can create a "branch" to test a crazy new feature. If it works, you merge it back. If it fails, you delete it, and the main project remains untouched.

1. HEAD: This is a pointer that says, "You are here." It points to the specific version (commit) you are currently looking at.

---

## The Three States: How Git "Saves"

To master Git, you must understand the journey a file takes. Imagine you are packing a box to ship:

| State | Definition | Analogy |
| --- | --- | --- |
| Working Directory | Files you are currently editing. | The items scattered on your desk. |
| Staging Area | A "waiting room" for your changes. | Placing items inside the shipping box. |
| Repository | The permanent database of snapshots. | Sealing the box and mailing it. |

---

## A Basic Developer Workflow (Hands-On)

Let's walk through a real-life scenario. You are starting a new web project. Open your terminal, and let's go.

### 1. Start the Engine

```bash
git init
```

What happened? You turned a regular folder into a Git Repository. A hidden .git folder was created to track your history.

### 2. Check the Situation

Bash

```plaintext
git status
```

What happened? This tells you what Git sees. If you have new files, Git will show them in red (Untracked). It sees them, but it isn't "watching" them yet.

### 3. Stage Your Files

Bash

```bash
git add index.html
# Or to add everything at once:
git add .
```

What happened? You moved your files into the Staging Area. They are now in the "box" and ready to be saved.

### 4. Save the Snapshot

Bash

```plaintext
git commit -m "Created the homepage layout"
```

What happened? You created a permanent save point. The files are now safely in the Repository. Always leave a message (-m) so you know what you did!

### 5. Look at History

Bash

```plaintext
git log
```

What happened? You’ll see a list of every commit with its unique ID, the author, the date, and your message.

---

## Guided Logic: Test Your Knowledge

Imagine you just finished a brilliant new feature. You run git commit -m "Added cool feature", but Git gives you an error saying "nothing to commit, working tree clean."

The Problem: You skipped a step. The Question: Based on the "Three States" table above, which command did you forget to run to move your code from the Working Directory to the Staging Area?

---

## Summary Checklist

Here is the daily rhythm of a developer:

1. Work on your code.

1. git status to see what changed.

1. git add . to prepare the changes (Stage).

1. git commit -m "message" to save the snapshot (Commit).

Happy coding!