Skip to content

Request: GitHub Support cleanup of my PR ref(s) (contributor email in commit metadata) #6000

Open

Description

@SergiuPogor

Hi, and thanks again for reviewing my contribution (#5125).

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:

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

  1. github-actions commented on Oct 30, 2026

    @github-actions
    Contributor

    🔴 Contributor Reputation Check: HIGH risk

    Check Risk
    Profile HIGH
    Credential audit NONE

    Maintainers: please review this contributor before merging.
    See the workflow run for full details.
    Automated check powered by AGT.

  2. SergiuPogor commented on Oct 31, 2026

    @SergiuPogor
    Author

    Hi, a follow-up on this, because it matters a lot to me: PR #5125 still exposes my work email through commit(s) fa8ea2cfb2, 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 #5125 (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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-review:HIGHContributor reputation check flagged HIGH risk

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions