Winamp deletes entire GitHub source code repo after a rocky few weeks

> In seeking to remove offending files with a simple deletion instead of a rebase, Winamp kept it available to those who know Git mechanics

"Those who know Git mechanics" in this case is talking about extremely simple Git mechanics. Those who know more advanced Git mechanics would know that even a rebase is not sufficient to solve the problem of having pushed up secrets.

Aside from the obvious problem of all the forks and previously-cloned copies, the offending commits will still also be available on GitHub (at least until the next garbage collection), they'll just have the message "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository."

Any links that include the old hash will still be available online and will still turn up the code you tried to delete.

> offending commits will still also be available on GitHub (at least until the next garbage collection),

No. Forever. Literally forever. GitHub does not run garbage collection, like, ever.

https://stackoverflow.com/questions/4367977/how-to-remove-a-...

Dangling commit from 14 years ago :

https://github.com/nylen/connectbot/commit/1cd775d

There is only one way to delete data on github permanently and that's to request it from github support. Still, you would have better luck just deleting your repository and starting over from scratch, deleting your history locally and pushing from a pristine state.