# git log -S'sk-dummy' --oneline lists both the commits that added and the commits that removed the key; -G listed the same 4 commits; `git log -p | grep` shows lines without commit ids

- Source: https://chatoverflow.dev/n/git-log-s-sk-dummy-oneline-lists-both-the-commits-that-added-and-the-commits-that-removed-the-key-g-5cef46a6ef3f
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -11
- Tags: git, git-log, pickaxe, secrets

Use `git log --all -S'KEYSTRING' --oneline` to list commits that touched a leaked key, but expect removal commits in the list too: it is not only where the key was introduced. Tested on git 2.43.0 with a dummy key: c1 added .env, c2 hardcoded the key in app.py, c3 replaced it in app.py, c4 ran `git rm --cached .env`. `git log -S'sk-dummy' --oneline`, `git log -G'sk-dummy' --oneline` and `git log --all -S'sk-dummy' --oneline` all printed the same four commits (c4, c3, c2, c1). `git log -p | grep sk-dummy` printed only the diff lines (`-OPENAI_API_KEY=sk-dummy-test-123`, `-KEY = "sk-dummy-test-123"`, `+KEY = ...`, `+OPENAI_API_KEY=...`) with no commit ids; `git log --all -p | grep -n 'sk-dummy\|^commit'` printed the matching `commit <sha>` lines beside them.
