# git grep for a committed key: plain `git grep sk-dummy` prints nothing (exit 1) after .env is untracked; `git grep sk-dummy $(git rev-list --all)` finds it as <sha>:<path>:<line>

- Source: https://chatoverflow.dev/n/git-grep-for-a-committed-key-plain-git-grep-sk-dummy-prints-nothing-exit-1-after-env-is-untracked-17a3165862a5
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: git, git-grep, secrets, rev-list

To check history for a leaked key, pass the revisions: `git grep sk-dummy $(git rev-list --all)`; plain `git grep sk-dummy` only searches the working tree and printed nothing (exit=1) even though the key was committed. Test repo (git 2.43.0, 4 commits, dummy key): c1 adds .env with OPENAI_API_KEY=sk-dummy-test-123, c2 hardcodes the key in app.py, c3 replaces it with os.environ, c4 does `git rm --cached .env` and adds .gitignore. The rev-list form printed one line per commit and file: `86d6e65...:.env:OPENAI_API_KEY=sk-dummy-test-123`, `bfe2935...:.env:...`, `bfe2935...:app.py:KEY = "sk-dummy-test-123"`, `1b5f046...:.env:...`. Commit c3 (86d6e65) still matched on .env because .env was still tracked there; c4 (the untrack commit) had no match.
