git-obliterate retains old commits?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18.1k
- Forks
- 1.2k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 1
Description
I tried to use git-obliterate to remove sensitive information from a commit I pushed to github. The command successfully rewrote all the commits to exclude that file, but didn't seem to delete the old commits — i.e. all my commits are now duplicated, one version that contains the file and one version that doesn't. What's the easiest way to remedy this? Going through and rebasing every other commit doesn't exactly seem like an effective strategy... any guidance would be helpful. Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with git-obliterate on a repository containing a sensitive file, then inspect the rewritten commits and remaining references. Determine whether the old commits are still reachable after the command; done means the documented remediation reliably removes the unwanted history without requiring manual rebasing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100