Delete the repo or contact GitHub Deleting the repo and recreating it without the bad commit seems to work if you can afford losing all issues. The data also disappears from the commit API (although push events are still visible). See also: https://stackoverflow.com/a/32840254/895245 If you can’t afford to lose issue data, GitHub support can manually … Read more
Last time I looked at this I stumbled across this thread, specifically this part: You can also end up with dangling objects in packs. When that pack is repacked, those objects will be loosened, and then eventually expired under the rule mentioned above. However, I believe gc will not always repack old packs; it will … Read more
To remove all dangling commits (including those still reachable from stashes and other reflogs) do this: git reflog expire –expire-unreachable=now –all git gc –prune=now But be certain that this is what you want. I recommend you read the man pages but here is the gist: git gc removes unreachable objects (commits, trees, blobs (files)). An … Read more
During the course of working with your Git repository, you may end up backing out of operations, and making other moves that cause intermediary blobs, and even some things that Git does for you to help avoid loss of information. Eventually (conditionally, according to the git gc man page) it will perform garbage collection and … Read more