git add for staging files - Commands & Configuration

Introduction

When you make changes to files in a project, you need to tell Git which changes you want to include in the next snapshot. The git add command lets you pick these changes and prepare them for saving.

When you have edited files and want to include those changes in your next commit.

When you want to add new files to your project so Git starts tracking them.

When you want to remove files from the project and prepare that removal for the next commit.

When you want to selectively choose some changes but not others before saving.

When you want to check what files are staged before committing.

Commands

This command stages the file named example.txt, telling Git to include its current changes in the next commit.

Terminal

git add example.txt

Expected Output

No output (command runs silently)

This stages all changed files in the current folder and its subfolders, preparing all your edits for the next commit.

Terminal

git add .

Expected Output

No output (command runs silently)

Shows which files are staged and which are not, so you can verify what will be saved in the next commit.

Terminal

git status

Expected Output

On branch main

Changes to be committed:

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



	new file:   example.txt



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:   README.md

Starts an interactive mode where you can choose which parts of changed files to stage, useful for fine control.

Terminal

git add -p

Expected Output

diff --git a/example.txt b/example.txt

index e69de29..d95f3ad 100644

--- a/example.txt

+++ b/example.txt

@@ -0,0 +1,2 @@

+Hello

+World

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

→

-p - Interactively choose chunks of changes to stage

Key Concept

If you remember nothing else from this pattern, remember: git add prepares your changes so Git knows exactly what to save in the next commit.

Common Mistakes

Running git commit without running git add first

Git will commit only the changes that were staged before, so new edits won't be saved.

Always run git add on the files you want to include before committing.

Using git add . without checking what files are staged

You might accidentally stage unwanted files or changes, leading to messy commits.

Use git status to review staged files before committing.

Trying to stage deleted files without using git add

Git won't track file removals unless you stage them explicitly.

Use git add on deleted files or use git rm to stage removals.

Summary

git add stages changes so Git knows what to include in the next commit.

You can stage individual files, all files, or parts of files with git add.

Use git status to check which files are staged before committing.

Practice

1. What does the git add command do in Git?

easy

A. It creates a new branch.

B. It stages changes to be included in the next commit.

C. It deletes files from the repository.

D. It permanently saves changes to the repository.

Solution

1. Step 1: Understand the purpose of git add

   The git add command is used to stage changes, which means preparing files to be saved in the next commit.

2. Step 2: Differentiate from other Git commands

   Unlike committing, which saves changes permanently, git add only marks files to be included in the next commit.

3. Final Answer:

   It stages changes to be included in the next commit. -> Option B

4. Quick Check:

   Staging = Preparing files for commit [OK]

Hint: Remember: add = prepare files, commit = save files [OK]

Common Mistakes:

• Confusing staging with committing
• Thinking git add deletes files
• Believing git add creates branches

2. Which of the following is the correct syntax to stage a single file named index.html?

easy

A. git stage index.html

B. git add -commit index.html

C. git commit index.html

D. git add index.html

Solution

1. Step 1: Recall the basic git add syntax

   The correct command to stage a file is git add <filename>. Here, the filename is index.html.

2. Step 2: Identify incorrect options

   Options A, B, and D use wrong commands or flags: -commit is invalid for git add, git stage is not a Git command, and git commit commits changes, not stages them.

3. Final Answer:

   git add index.html -> Option D

4. Quick Check:

   Stage single file = git add filename [OK]

Hint: Use 'git add filename' to stage one file [OK]

Common Mistakes:

• Using 'git commit' instead of 'git add' to stage
• Adding invalid flags like '-commit' with 'git add'
• Using non-existent commands like 'git stage'

3. Given these commands run in order:

echo 'Hello' > file1.txt
echo 'World' > file2.txt
git add file1.txt
git status

What will git status show about file1.txt and file2.txt?

medium

A. Both file1.txt and file2.txt are staged.

B. Both files are untracked.

C. file1.txt is staged; file2.txt is untracked.

D. file2.txt is staged; file1.txt is untracked.

Solution

1. Step 1: Analyze the commands executed

   Two files are created: file1.txt and file2.txt. Then only file1.txt is staged using git add file1.txt.

2. Step 2: Understand git status output

   git status will show file1.txt as staged (ready to commit) and file2.txt as untracked (not staged).

3. Final Answer:

   file1.txt is staged; file2.txt is untracked. -> Option C

4. Quick Check:

   Only added files are staged [OK]

Hint: Only files added with 'git add' are staged [OK]

Common Mistakes:

• Assuming all new files are staged automatically
• Confusing staged and untracked files
• Thinking 'git add' stages all files without specifying

4. You run git add *.txt but get an error: fatal: pathspec '*.txt' did not match any files. What is the most likely cause?

medium

A. There are no files ending with .txt in the current directory.

B. You need to use git add --all instead.

C. The command should be git add '*.txt' with quotes.

D. Git does not support wildcards in git add.

Solution

1. Step 1: Understand the error message

   The error says no files match '*.txt', meaning no files with .txt extension exist in the current folder.

2. Step 2: Evaluate other options

   Using quotes (The command should be git add '*.txt' with quotes.) or --all (You need to use git add --all instead.) won't help if no matching files exist. Git does not support wildcards in git add. is incorrect because Git supports wildcards via shell expansion.

3. Final Answer:

   There are no files ending with .txt in the current directory. -> Option A

4. Quick Check:

   No matching files = error [OK]

Hint: Check if files exist before using wildcards [OK]

Common Mistakes:

• Assuming Git handles wildcards internally
• Using quotes that prevent shell expansion
• Confusing git add --all with wildcard usage

5. You want to stage all modified and new files in your project except files in the logs/ folder. Which command correctly stages the files?

hard

A. git add . ':!logs/'

B. git add --all -- ':!logs/'

C. git add . && git reset --hard logs/

D. git add . && git rm -r --cached logs/

Solution

1. Step 1: Understand how to exclude a folder when staging

   Git allows pathspec exclusions using :!folder/ syntax after the paths to add. So git add . ':!logs/' stages all except logs/.

2. Step 2: Analyze other options

   git add --all -- ':!logs/' uses invalid syntax with --all -- ':!logs/'. git add . && git reset --hard logs/ uses git reset --hard which discards changes in the working directory of logs/, not just unstaging. git add . && git rm -r --cached logs/ removes logs/ from Git tracking, which is destructive.

3. Final Answer:

   git add . ':!logs/' -> Option A

4. Quick Check:

   Use pathspec exclusion ':!folder/' to skip files [OK]

Hint: Use ':!folder/' to exclude paths in git add [OK]

Common Mistakes:

• Using 'git rm' instead of excluding paths
• Trying unsupported flags for exclusion
• Forgetting quotes around pathspec exclusions