🧨 The Problem: .env File in Git History

While working on my LeetcodeClone project, I mistakenly pushed my .env file (containing API keys and database credentials) to multiple branches (class1, class2, class3) and merged them into main.

I tried:

git rm --cached .env

But this only removed it from future commits—the file still existed in Git history! I needed a way to completely erase it from all commits to prevent security risks.

❌ Failed Attempts

Using git filter-branch (Deprecated & Dangerous)

git filter-branch --force --index-filter "git rm --cached --ignore-unmatch .env" --prune-empty --tag-name-filter cat -- --all

This worked, but:

• Extremely slow on large repos

• Can corrupt history if not done carefully

• Git itself recommends against it

Tried git-filter-repo but Got Errors

git filter-repo --path .env --invert-paths

Error:

Aborting: Refusing to destructively overwrite repo history since
this does not look like a fresh clone.

Turns out, git-filter-repo requires a fresh clone for safety.

✅ The Solution: Using git filter-repo Correctly

Step 1: Clone a Fresh Copy (Mirror Mode)

git clone --mirror git@github.com:yourusername/LeetcodeClone.git LeetcodeClone_Mirror
cd LeetcodeClone_Mirror

--mirror ensures a bare repository, which filter-repo prefers.

Step 2: Run git filter-repo to Remove .env

git filter-repo --path .env --invert-paths --force

Explanation:

• --path .env → Targets the file

• --invert-paths → Removes it from all commits

• --force → Overrides safety checks (since we’re in a mirror clone)

Success Output:

New history written in 0.19 seconds; now repacking/cleaning...
Completely finished after 1.70 seconds.

Step 3: Force Push to Remote

git push origin --force --all
git push origin --force --tags

⚠️ Warning: This rewrites history, so collaborators must reclone the repo.

Step 4: Prevent Future .env Commits

Add .env to .gitignore:

echo ".env" >> .gitignore
git add .gitignore
git commit -m "Add .env to .gitignore"
git push

💡 Alternative: BFG Repo Cleaner (Easier for Simple Cases)

If git-filter-repo is too complex, try BFG Repo Cleaner:

java -jar bfg.jar --delete-files .env .git
git reflog expire --expire=now --all
git gc --prune=now --aggressive
git push --force

🔍 Final Verification

Ensure .env is completely gone:

git log --all -- .env         # Should return nothing
git grep .env $(git rev-list --all) # No matches