[jasonpeacock]

Those keys absolutely need to be rotated, regardless of whether you delete the commit or repo after accidentally pushing them.

At which point you may as well leave them there...

[labawi]

Keys probably aren't the best example. What about PII, accidentally committed "test" data, documents, nudes, whatever..

[jasonpeacock]

If repos are public, then you must assume that once something is pushed then someone has copied it.

You may get lucky and remove/hide it fast enough, or think you did...

This is an with Github today, all public repos are being watched by bots reviewing all commits for accidentally-pushed credentials.

The only solution is to not use a public repo.

[olah_1]

You’re not answering the question. Is it possible to delete or not?

On GitHub yes someone might be watching, but deletes are still possible.

[jasonpeacock]

I don't know. You can always clean the Git history & force-push it, but the developers would have to explain if there's any backups or archive kept anywhere...

[htrap]

Since data is stored permanently on Arweave, there's no way to remove it from the blockchain. However, you could force push your repo which would remove your concerned commit from Gitopia repository view.

[olah_1]

I agree, but is it possible to delete at all on ARWeave? Let’s say someone accidentally puts their full name and address in a repo.