https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository#fully-removing-the-data-from-githubContact us through the GitHub Support portal, and provide the following information:
The owner and repository name in question (e.g. YOUR-USERNAME/YOUR-REPOSITORY).
The number of affected pull requests, found in the previous step. This is used by Support to verify you understand how much will be affected.
The First Changed Commit(s) reported by git-filter-repo (Look for NOTE: First Changed Commit(s) in its output.)
If NOTE: There were LFS Objects Orphaned by this rewrite appears in the git-filter-repo output (right after the First Changed Commit), then mention you had LFS Objects Orphaned and upload the named file to the ticket as well.
If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:
Dereference or delete any affected PRs on GitHub.
Run a garbage collection on the server to expunge the sensitive data from storage.
Remove cached views.
If LFS Objects are involved, delete and/or purge the orphaned LFS objects.
Important
GitHub Support won't remove non-sensitive data, and will only assist in the removal of sensitive data in cases where we determine that the risk can't be mitigated by rotating affected credentials.