git add with patterns and directories - Commands & Configuration

Introduction

When you change files in a project, you need to tell Git which files to save for the next snapshot. Using patterns and directories with git add helps you quickly select many files without naming each one.

When you want to add all files in a folder to your next commit.

When you want to add only files with a certain extension, like all .txt files.

When you want to add files that match a pattern, like all files starting with 'test'.

When you want to add changes in multiple folders at once.

When you want to avoid adding unwanted files by specifying exactly which files to include.

Commands

This command adds all files and folders inside the 'docs' directory to the staging area, preparing them for the next commit.

Terminal

git add docs/

Expected Output

No output (command runs silently)

This adds all files ending with .txt in the current directory to the staging area. The quotes prevent the shell from expanding the pattern before Git sees it.

Terminal

git add '*.txt'

Expected Output

No output (command runs silently)

This adds all JavaScript files inside the 'src' directory to the staging area.

Terminal

git add src/*.js

Expected Output

No output (command runs silently)

This adds all files and folders starting with 'test' in the current directory to the staging area.

Terminal

git add 'test*'

Expected Output

No output (command runs silently)

Shows which files are staged and ready to be committed, confirming that the correct files were added.

Terminal

git status

Expected Output

On branch main

Changes to be committed:

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



	new file:   docs/readme.md

	new file:   notes.txt

	new file:   src/app.js

	new file:   test_script.sh

Key Concept

If you remember nothing else from this pattern, remember: git add can use folder names and file patterns to quickly select many files at once.

Common Mistakes

Not using quotes around patterns like '*.txt'

The shell expands the pattern before Git sees it, which can cause errors or no files added if no matches exist.

Always put quotes around patterns to let Git handle the matching.

Trying to add a directory without a trailing slash

Git may not recognize it as a directory and fail to add its contents.

Always include the trailing slash when adding directories, like 'git add docs/'.

Adding too broad a pattern and including unwanted files

You might stage files you did not intend to commit, causing confusion or errors.

Use specific patterns or check with 'git status' before committing.

Summary

Use 'git add directory/' to stage all files inside a folder.

Use 'git add "*.ext"' with quotes to stage files matching a pattern.

Check staged files with 'git status' before committing.

Practice

1. What does the command git add src/ do?

easy

A. Removes the 'src' directory from the repository.

B. Stages only the 'src' directory itself, not its contents.

C. Commits changes in the 'src' directory immediately.

D. Stages all changes in the 'src' directory and its subdirectories.

Solution

1. Step 1: Understand the command context

   The command git add src/ targets the directory named 'src'.

2. Step 2: Know how git add works with directories

   Git stages all files and subdirectories inside 'src' recursively when adding a directory.

3. Final Answer:

   Stages all changes in the 'src' directory and its subdirectories. -> Option D

4. Quick Check:

   git add directory = stage all inside [OK]

Hint: Adding a directory stages all files inside it recursively [OK]

Common Mistakes:

• Thinking it stages only the directory, not contents
• Confusing add with commit
• Assuming it deletes files

2. Which of the following is the correct command to stage all .txt files in the current directory using a pattern?

easy

A. git add txt.*

B. git add .txt*

C. git add *.txt

D. git add *txt

Solution

1. Step 1: Understand wildcard usage in git add

   The asterisk (*) matches any characters, so *.txt matches all files ending with '.txt'.

2. Step 2: Check each option's pattern

   git add *.txt correctly matches all '.txt' files. Others do not match the intended pattern.

3. Final Answer:

   git add *.txt -> Option C

4. Quick Check:

   Use * before extension to match all files [OK]

Hint: Use '*.ext' to add all files with that extension [OK]

Common Mistakes:

• Placing * after extension instead of before
• Using wrong order of characters in pattern
• Confusing dot placement in patterns

3. Given the directory structure:

project/
  ├─ app.js
  ├─ README.md
  └─ docs/
      ├─ intro.md
      └─ setup.md

What files will be staged after running git add docs/*.md?

medium

A. Only docs/intro.md and docs/setup.md

B. All files in project including app.js and README.md

C. No files, command fails due to pattern

D. Only docs/setup.md

Solution

1. Step 1: Analyze the pattern used

   The pattern docs/*.md matches all files ending with '.md' inside the 'docs' directory only.

2. Step 2: Identify matching files

   Inside 'docs', 'intro.md' and 'setup.md' match. Files outside 'docs' are not matched.

3. Final Answer:

   Only docs/intro.md and docs/setup.md -> Option A

4. Quick Check:

   Pattern matches files only inside specified directory [OK]

Hint: Pattern 'dir/*.ext' adds matching files only inside that directory [OK]

Common Mistakes:

• Assuming files outside 'docs' are staged
• Thinking pattern matches recursively
• Believing command fails if pattern matches multiple files

4. You run git add docs/*.md but only docs/intro.md is staged, not docs/setup.md. What is the most likely cause?

medium

A. You need to add files one by one manually.

B. The file docs/setup.md is ignored by .gitignore.

C. Git add cannot stage files in subdirectories.

D. The pattern '*.md' only matches one file at a time.

Solution

1. Step 1: Understand why some files are not staged

   If a file is ignored by .gitignore, git add will skip it even if the pattern matches.

2. Step 2: Check other options for correctness

   Patterns can match multiple files; git add works recursively for directories; manual adding is not required.

3. Final Answer:

   The file docs/setup.md is ignored by .gitignore. -> Option B

4. Quick Check:

   Ignored files are skipped by git add [OK]

Hint: Check .gitignore if some matching files are not staged [OK]

Common Mistakes:

• Believing patterns match only one file
• Thinking git add can't stage multiple files
• Assuming manual add is always needed

5. You want to stage all JavaScript files in the 'src' directory and all Markdown files in the 'docs' directory with one command. Which command achieves this?

hard

A. git add src/*.js docs/*.md

B. git add 'src/*.js docs/*.md'

C. git add src/*.js && git add docs/*.md

D. git add src/ docs/ *.js *.md

Solution

1. Step 1: Understand how to add multiple patterns in one command

   Git add accepts multiple paths or patterns separated by spaces without quotes.

2. Step 2: Evaluate each option

   git add src/*.js docs/*.md correctly lists both patterns separated by space. git add 'src/*.js docs/*.md' quotes patterns unnecessarily, which may cause shell to treat them literally. git add src/*.js && git add docs/*.md runs two commands, not one. git add src/ docs/ *.js *.md mixes directories and patterns incorrectly.

3. Final Answer:

   git add src/*.js docs/*.md -> Option A

4. Quick Check:

   Multiple patterns separated by space work in one git add [OK]

Hint: List multiple patterns separated by spaces in one git add command [OK]

Common Mistakes:

• Using quotes that prevent shell expansion
• Trying to combine commands with && instead of one command
• Mixing directories and patterns incorrectly