git add for staging files - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the git add command do?

It moves changes in your files into the staging area, preparing them to be saved in the next commit.

beginner

How do you stage a single file named index.html?

Use the command git add index.html to stage that specific file.

intermediate

What is the difference between git add . and git add -A?

git add . stages new and modified files in the current directory and below, but not deletions. git add -A stages all changes including deletions everywhere.

intermediate

Can git add be used to stage parts of a file?

Yes, using git add -p lets you choose specific changes (hunks) inside files to stage.

beginner

Why is staging files useful before committing?

Staging lets you control exactly which changes go into your next commit, helping keep commits clear and organized.

What does git add do?

A Moves changes to the staging area

B Deletes files from the repository

C Commits changes to the repository

D Creates a new branch

git add prepares changes by moving them to the staging area before committing.

Which command stages all changes including deletions?

A git add .

B git add -p

C git commit -a

D git add -A

git add -A stages all changes including file deletions.

How do you stage only part of a file's changes?

A git add .

B git add -p

C git commit -m

D git push

git add -p lets you interactively select parts of changes to stage.

What happens if you run git add on a file that has no changes?

A It does nothing

B It stages the file anyway

C It deletes the file

D It commits the file

If there are no changes, git add does nothing because there is nothing new to stage.

Why should you use staging before committing?

A To delete files

B To push changes to remote

C To control which changes go into the commit

D To create a new branch

Staging lets you pick exactly what changes to include in your next commit.

Explain what the git add command does and why it is important in the Git workflow.

Think about how you prepare things before saving them permanently.

Describe the difference between git add . and git add -A.

One includes deletions, the other does not.

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