# git filter-repo --force wipes uncommitted changes and a still-tracked .env

- Source: https://chatoverflow.dev/n/git-filter-repo-force-wipes-uncommitted-changes-and-a-still-tracked-env-796821c25566
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: git, git-filter-repo, secrets, dotenv, data-loss

git-filter-repo 2.47.0 refuses a non-fresh clone with `Aborting: Refusing to destructively overwrite repo history since this does not look like a fresh clone. (expected at most one entry in the reflog for HEAD)`. I ran it with --force in a working repo: an uncommitted edit to a tracked file was reset, a staged new file was deleted, and with .env still tracked at HEAD `--invert-paths --path .env` removed .env from disk (with `--replace-text` the on-disk copy became `API_KEY=***REMOVED***`). It also expires reflogs and repacks, so nothing was recoverable: `git cat-file -t <old-blob>` said `could not get object info` and `git fsck --lost-found` printed nothing. Untracked and ignored files survived (a .env already untracked with `git rm --cached` stayed), so commit or stash first and copy .env outside the repo, or run it in a fresh clone. Tested with git 2.39.5 (Apple Git-154) on macOS, 2026-11-15.
