What is the difference between git add and git commit?

git add stages files (staging area), git commit permanently records the staged files in the project history. Add = put items in your cart, commit = place the order.

What does git add . (with a dot) do?

The dot means "the entire current directory". git add . stages all modified, new, and deleted files in the current directory and its subdirectories.

Can you undo a git add?

Yes, with git restore --staged file or git reset HEAD file. The changes remain in your working directory, they are just removed from staging.

Do I always need to run git add before git commit?

Yes, unless you use git commit -a which automatically stages already-tracked modified files. But new files always need to go through git add first.

What is the staging area?

It is an intermediate zone between your working directory (your files) and the Git history. It lets you choose exactly what you want to include in your next commit.

Git add: stage files for your next commit

Before committing, you need to tell Git which files to include. git add places your changes in the staging area, ready for the next commit.

Practice git add Git Glossary

gitquest — enquête

Fundamental

What is git add?

git add is the bridge between your working directory and the next commit. It places changes in the staging area (also called the index).

Think of it like shopping: you put items in your cart (git add) before checking out (git commit). You can add or remove items as many times as you want before confirming.

Without git add, your changes will not be included in the next commit. It's the most fundamental command after git init.

The Git workflow in 3 steps

Working Directory

Your local files, modified or new

↓ git add

Staging Area (Index)

Files ready to be committed

↓ git commit

History

Commits permanently recorded

Git add in practice

Add specific files or the entire directory.

Add specific files

gitquest — git add

# Add files to the staging area

$git status

modified: index.html

new file: style.css

$git add index.html style.css

$git status

modified: index.html

new file: style.css

(use "git restore --staged <file>..." to unstage)

Add all or by pattern

gitquest — git add advanced

# Add all modified files

$git add .

All modified files added to staging

# Or add by pattern

$git add *.css

CSS files added to staging

# Add interactively

$git add -p

diff --git a/index.html b/index.html

Stage this hunk [y,n,q,a,d,e,?]?

Essential add commands

git add file

Stage a specific file

git add .

Stage the entire current directory

git add -A

Stage everything (including deletions)

git add -p

Interactive patch-by-patch mode

git add *.ext

Stage by pattern (glob)

git add -u

Stage tracked modified files

Common mistakes with git add

git add . without a .gitignore

You risk adding node_modules, .env, build files... Always create a .gitignore before your first git add.

Forgetting git add before git commit

If you commit without add, nothing happens. Git only commits what is in the staging area.

Confusing add and commit

git add does not save anything to the history. It's git commit that creates the permanent snapshot.

Part of the Git Basics guide

Related commands

git status

Check what is staged

git commit

Record staged files

git restore

Unstage files

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

Questions about git add

Master staging with GitQuest

Learn to prepare your commits like a pro with GitQuest's interactive challenges.

Get started now