Staging area (index) purpose in Git - Commands & Configuration

Introduction

When you change files in a project, you need a way to choose which changes to save next. The staging area is like a waiting room where you put changes before saving them permanently. It helps you organize and control what goes into your project history.

When you want to prepare only some changes for the next save, not all at once.

When you fix multiple bugs but want to save each fix separately for clarity.

When you want to review your changes before saving them to avoid mistakes.

When you want to group related changes together before saving.

When you want to undo some changes from the next save without losing them.

Commands

Shows which files have changes and which are staged for the next save.

Terminal

git status

Expected Output

On branch main

Changes not staged for commit:

  (use "git add <file>..." to update what will be committed)

  (use "git restore <file>..." to discard changes in working directory)

	modified:   example.txt



no changes added to commit (use "git add" and/or "git commit -a")

Moves changes in example.txt to the staging area, preparing them for the next save.

Terminal

git add example.txt

Expected Output

No output (command runs silently)

Checks that example.txt is now staged and ready to be saved.

Terminal

git status

Expected Output

On branch main

Changes to be committed:

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

	modified:   example.txt

Saves the staged changes permanently in the project history with a message.

Terminal

git commit -m "Update example.txt with new info"

Expected Output

[main abc1234] Update example.txt with new info

 1 file changed, 3 insertions(+), 1 deletion(-)

→

-m - Adds a message describing the changes being saved

Key Concept

The staging area lets you pick exactly which changes to save next, giving you control and clarity over your project history.

Common Mistakes

Trying to save changes without adding them to the staging area first

Git will not include unstaged changes in the save, so your changes won't be recorded.

Use 'git add' to stage the changes before committing.

Adding all files without checking what is staged

You might save unwanted changes or incomplete work, making history messy.

Use 'git status' to review changes and add only what you want.

Summary

Use 'git add' to move changes into the staging area before saving.

'git status' helps you see what is staged and what is not.

'git commit' saves only the staged changes with a message.