What is the difference between git grep and grep?

git grep only searches in files tracked by Git (ignores node_modules, build, etc.). It is also faster because it uses the Git index. grep searches all files on the system.

How do I search case-insensitively?

Use the -i flag: git grep -i "todo" will find TODO, todo, Todo, etc. It is the same flag as regular grep.

Can I search in an old commit?

Yes, add the commit hash after the pattern: git grep "pattern" a1b2c3d. You can also search in a tag: git grep "pattern" v1.0.

How do I search a pattern in a specific file type?

Use -- with a glob: git grep "pattern" -- "*.js" for JS files, or git grep "pattern" -- "src/**" for a specific directory.

How do I search with a regular expression?

git grep supports regex by default. Use -E for extended regular expressions (ERE): git grep -E "function\s+\w+". Use -P for Perl-compatible regex (PCRE).

Git grep: search through source code

git grep searches for text in files tracked by Git. Faster than regular grep, it automatically ignores node_modules and untracked files.

Practice git grep Git Glossary

gitquest — enquête

What is git grep?

git grep searches for text in files tracked by Git. It is like grep but optimized for Git repositories.

The advantage: it automatically ignores untracked files (node_modules, build, .env) and can even search in old commits.

Git grep syntax

git grep "pattern"

Search in all tracked files

git grep -n "pattern"

With line numbers

git grep "pattern" -- "*.js"

Search only in JS files

Git grep in practice

Basic and advanced searches.

Basic search

gitquest — git grep

# Search for a word across the whole project

$git grep "TODO"

src/index.js:42: // TODO: add validation

src/utils.js:15: // TODO: optimize this function

tests/app.test.js:8: // TODO: add more tests

# Search with line numbers

$git grep -n "fetchData"

src/api.js:23:async function fetchData(url) {

src/app.js:67: const data = await fetchData('/users')

Advanced search

gitquest — git grep advanced

# Search in a specific commit

$git grep "config" HEAD~5

HEAD~5:src/config.js:1:const config = {...}

# Search only in JS files

$git grep "import" -- "*.js"

src/app.js:1:import React from 'react'

# Count occurrences per file

$git grep -c "console.log"

src/debug.js:12

src/app.js:3

Essential grep commands

git grep -i "word"

Case-insensitive search

git grep -n "word"

With line numbers

git grep -c "word"

Count occurrences per file

git grep -l "word"

List only file names

git grep -w "var"

Whole word (no substring)

git grep -E "regex"

Extended regular expression

Common mistakes with git grep

Searching in untracked files

git grep only searches tracked files. For untracked files, use git grep --untracked or regular grep.

Forgetting quotes around the pattern

Without quotes, the shell may interpret special characters. Always wrap the pattern in quotes: git grep "pattern".

Not using file filters

On large projects, filter by file type with -- "*.ext" for more relevant and faster results.

Part of the Git History, Search & Debug guide

Related commands

git log

Search through commit history

git blame

See who wrote each line

git bisect

Find the commit that broke things

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

Questions about git grep

Master code search with GitQuest

Learn to dig through code and history like a detective.

Start the investigations