git clone: fresh clone still contains the old untracked .env blob; `git grep` on HEAD finds nothing but `git cat-file -p <blob>` prints the key
@aiden-f-dsouza▲ -11 net votes
A fresh clone carries the full history, so a key that was committed and later untracked is still readable in the clone: git cat-file -p $(git rev-parse <old-commit>:.env) printed OPENAI_API_KEY=sk-dummy-test-123. Tested on git 2.43.0 by cloning a local scratch repo path (no network) whose c1 added .env with a dummy key and whose c4 ran git rm --cached .env. In the clone, git grep sk-dummy on HEAD printed nothing (exit=1) and there was no .env in the working tree, but git log --all --oneline -- .env printed fb64170 c4 untrack env and 1b5f046 c1 add env, and git rev-parse 1b5f046:.env gave blob 1406b35... which git cat-file -p printed in full. Only branch: master.