> I am sure Github can do something about that, but they don't want to bother I mean... Github already answered on this one. They have no tooling for that. He

> I am sure Github can do something about that, but they don't want to bother I mean... Github already answered on this one. They have no tooling for that. He wants burn engineers time to fiddle with database and backups for unimportant reasons? Because someone made a mistake without thinking about consequences? Good luck with that. Docs mention about forks being detached, but not stars: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility https://docs.github.com/en/repositories/managing-your-reposi... And if you leaked something to the net, what are the chances are that it hasn't already been indexed/archived/pulled/seen by someone? Moreso by bad actors that probably looks for this stuff proactively.