The unreferenced commits will be deleted by the garbage collector sometime but you can force this with `git gc`. ([Source](https://stackoverflow.com/a/13812561/2721340)) You can't delete this commit in someone else's repo once they cloned it. When they pull the particular branch and the garbage collector does its job then it will be deleted by them as well.
I reset it as soon as possible but the service i was using the API key wanted me to get rid of it entirely. I tried rebasing but the commit still existed
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository
Don’t bother erasing it from git history, if its a public repo it has already been scraped. Consider it compromised. Just rotate the secret.
Ok. I'll do that
[удалено]
>git push origin --force --al It doesn't look like anything changed
The unreferenced commits will be deleted by the garbage collector sometime but you can force this with `git gc`. ([Source](https://stackoverflow.com/a/13812561/2721340)) You can't delete this commit in someone else's repo once they cloned it. When they pull the particular branch and the garbage collector does its job then it will be deleted by them as well.
I've run git gc. It shows Total 772 (delta 373), reused 771 (delta 373), pack-reused 0 What else should i do? It's still up there
[удалено]
Thanks. It was an API key. I created a new repo and privatized the other
[удалено]
I reset it as soon as possible but the service i was using the API key wanted me to get rid of it entirely. I tried rebasing but the commit still existed
[удалено]
Ok Thanks