Hacker News new | ask | show | jobs
by zegerjan 2337 days ago
The reason you couldn't delete the blob, is because someone forked your repository and GitHub uses git alternates for deduplication of fork networks.

I think you could ask GitHub if you can recreate your repository without the offending blob, and you should be good again.
1 comments
aliostad 2336 days ago
This is essentially what I did using bfg tool. They still took it down.

https://help.github.com/en/github/authenticating-to-github/r...

link
zegerjan 2336 days ago
I'm saying the blob was in a new repository, you had no control over. You couldn't have removed it, you could only make sure it doesn't get referenced in _your_ repository. Which is what you did.
link
aliostad 2336 days ago
sure, but I imagine they have already removed those forks too.

Have a look at this list https://github.com/github/dmca/blob/master/2020/01/2020-01-2...

link