git grep

The Hook (The "Byte-Sized" Intro)

grep searches your filesystem. git grep searches only your tracked files — skipping node_modules, build outputs, and everything in .gitignore. It's faster, cleaner, and repo-aware. Need to find every file that uses validateToken? git grep finds them in milliseconds, even in a repo with 100,000 files.

📖 What is git grep?

git grep searches the content of files tracked by Git. It's faster than regular grep because it only scans tracked files and uses Git's internal index for speed.

Conceptual Clarity

git grep vs regular grep:

Feature	`grep -r`	`git grep`
Searches	All files recursively	Only tracked files
Ignores `.gitignore`	❌	✅ Automatic
Speed	Slower (scans everything)	Faster (uses index)
Search old versions	❌	✅ `git grep <term> <commit>`

Useful flags:

Flag	What It Does
`-n`	Show line numbers
`-c`	Count matches per file
`-l`	List filenames only
`-i`	Case-insensitive
`-w`	Match whole words only
`-e`	Specify pattern (for complex patterns)
`--and` / `--or`	Combine patterns

Real-Life Analogy

grep is searching your entire house for your keys. git grep is searching only the rooms you actually use — ignoring the attic, garage, and storage unit.

Visual Architecture

flowchart LR QUERY["🔍 Search term"] --> GITGREP["git grep"] GITGREP --> TRACKED["Only tracked files"] TRACKED --> RESULTS["📄 Matching lines"] style GITGREP fill:#0f3460,stroke:#53d8fb,color:#53d8fb style RESULTS fill:#1b2d1b,stroke:#53d8fb,color:#53d8fb

Why It Matters

Speed: Dramatically faster in large repos by skipping untracked files.
Clean results: No matches from node_modules, build/, or other ignores.
Historical search: Search code as it existed in any commit.
Multi-pattern: Combine patterns with --and / --or.

Code

bash

# ─── Basic search ───
git grep "validateToken"
# src/auth.js:42: const result = validateToken(token);
# src/middleware.js:15: if (validateToken(req.token)) {

# ─── With line numbers ───
git grep -n "validateToken"

# ─── Count matches per file ───
git grep -c "TODO"
# src/auth.js:3
# src/utils.js:1

# ─── List files only ───
git grep -l "API_KEY"

# ─── Case-insensitive ───
git grep -i "error"

# ─── Search in a specific commit ───
git grep "validateToken" v1.0.0
# Searches code as it existed at v1.0.0

# ─── Combine patterns ───
git grep -e "validate" --and -e "token"
# Lines matching BOTH "validate" AND "token"

# ─── Search specific file types ───
git grep "import" -- "*.js"

Key Takeaways

git grep searches only tracked files — faster and cleaner than grep -r.
Use -n for line numbers, -l for filenames, -c for counts.
Search historical versions: git grep "term" <commit>.
Combine with -- "*.ext" to search specific file types.

Interview Prep

Q: Why use git grep instead of regular grep? A: git grep only searches tracked files, automatically skipping ignored files (node_modules, build outputs). It's faster in large repos because it uses Git's index, and it can search code at any historical commit.
Q: How do you search for a string in a previous version of the code? A: git grep "string" <commit-sha-or-tag>. For example, git grep "validate" v1.0.0 searches the codebase as it existed at tag v1.0.0.
Q: How do you find files containing two different patterns? A: git grep -e "pattern1" --and -e "pattern2". This finds lines (or files with -l) that match both patterns.