Notes on using git-replace to get rid of giant objects

If you want to go the mentioned &quot;rewrite-whole-history&quot; route, I have used BFG Repo Cleaner [0] successfully in the past. It&#x27;s way faster than git-filter-branch [1].<p>Another thing: You can work with shallow clones. If the commit is ancient, no need to pull the whole history of a project.<p>[0]: <a href="https:&#x2F;&#x2F;rtyley.github.io&#x2F;bfg-repo-cleaner&#x2F;" rel="nofollow">https:&#x2F;&#x2F;rtyley.github.io&#x2F;bfg-repo-cleaner&#x2F;</a><p>[1]: <a href="https:&#x2F;&#x2F;git-scm.com&#x2F;docs&#x2F;git-filter-branch" rel="nofollow">https:&#x2F;&#x2F;git-scm.com&#x2F;docs&#x2F;git-filter-branch</a>

Maybe create a `new-master` branch with the offending commits rebased out; then automation to cherry-pick new commits between `master` to `new-master`.<p>Or change all CI &#x2F; dev docs to use `--depth`, and save more than 350MB per checkout in the process.

What would happen if you:<p>1. checkout the last commit before the bad one.<p>2. cherry-pick every commit after the bad one.<p>Would that get rid of the bad commit?

Fire the BFG. It&#x27;s a no-brainer.