git add for staging files - Mini Project: Build & Apply

Using git add to Stage Files

📖 Scenario: You are working on a small project and have created some new files and modified existing ones. Before you can save these changes in your project history, you need to stage them using git add. This is like putting your work into a basket before officially saving it.

🎯 Goal: Learn how to use git add to stage specific files and all files in your project directory.

📋 What You'll Learn

Create two new files named index.html and style.css.

Modify an existing file named README.md.

Use git add to stage the file index.html.

Use git add to stage all changed files.

Use git status to verify staged files.

💡 Why This Matters

🌍 Real World

Staging files with <code>git add</code> is a key step before saving changes in version control. It helps you control exactly what changes you want to save.

💼 Career

Understanding how to stage files is essential for software developers, DevOps engineers, and anyone working with code repositories to manage project history safely.

1

Create new files and modify README.md

Create two new files named index.html and style.css. Also, modify the existing file README.md by adding the line "Project started" at the end.

Git

# Create the files index.html and style.css
# Add the line "Project started" to README.md
# Your code here

Hint

Use echo commands to create and modify files.

2

Stage the file index.html using git add

Use the command git add index.html to stage only the file index.html.

Git

echo "" > index.html

echo "body { margin: 0; }" > style.css

echo "Project started" >> README.md

# Stage the file index.html
# Your code here

Hint

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

3

Stage all changed files using git add

Use the command git add . to stage all changed files including style.css and README.md.

Git

echo "" > index.html

echo "body { margin: 0; }" > style.css

echo "Project started" >> README.md

git add index.html

# Stage all changed files
# Your code here

Hint

Use git add . to stage all files in the current directory.

4

Check staged files with git status

Use the command git status to display the list of staged files and verify that index.html, style.css, and README.md are staged.

Git

echo "" > index.html

echo "body { margin: 0; }" > style.css

echo "Project started" >> README.md

git add index.html

git add .

# Check the status of staged files
# Your code here

Hint

Run git status to see which files are staged for commit.

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