Repository navigation
Request: GitHub Support cleanup of my PR ref(s) (contributor email in commit metadata) #73
Description
Hi, and thanks again for reviewing my contribution (#63).
By mistake, the original commit(s) of that pull request were made with my former employer's email address. Your branches are not affected and nothing in the repository needs to change. The old commits only survive in GitHub's pull request refs (refs/pull/N/head), which only GitHub Support can remove.
I've already asked GitHub Support myself, but they act much faster when the repository owner asks. If you could spare two minutes, please open a request at https://support.github.com/contact with:
- Repository:
ZeroPointRepo/GrokBotDev - PR Add CurlShot plugin #63, commit
4b4dffdad39f33a7d012c0758aca8426d909c9b2 - Ask: "Please dereference these commits from the pull request(s) and run garbage collection (sensitive data: a contributor's personal email in commit metadata)."
This follows GitHub's documented process: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository#fully-removing-the-data-from-github
Completely optional, and thank you very much!
Activity
SergiuPogor commentedon Oct 31, 2026
Hi, a follow-up on this, because it matters a lot to me: PR #63 still exposes my work email through commit(s)
4b4dffdad3, even though nothing is left in your branches.GitHub acts much faster when the repository owner asks. Two minutes at https://support.github.com/contact is enough: ask them to delete PR #63 (or dereference the commit(s) above) and run garbage collection, because of a contributor's personal email in commit metadata. Deleting the whole PR is completely fine with me, I don't need it kept. You can mention my ticket #4926271.
If you'd rather not, a one-line reply is all I need and I will stop asking. Thank you!