Urgent Security Request: Permanently Purge Sensitive Data from Closed Pull Request #179220
Replies: 1 comment
-
|
You can’t delete a pull request yourself, but since it contains sensitive credentials, contact GitHub Support via this page |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
General
Body
Hello GitHub Support Team,
I am writing to request the permanent and complete deletion of a closed pull request from my repository, as it contains exposed sensitive credentials.
During development, a Firebase API key was accidentally committed and pushed to a pull request. I have since followed the documentation to remove the sensitive data from my branch's history using git filter-repo and have force-pushed the clean history to the branch.
However, the sensitive key remains visible in the commit history of the closed pull request, which is a significant security vulnerability.
For the security and integrity of my project, I urgently request that you permanently purge the following pull request and all its associated history from your systems.
Here are the details:
I understand that this action is irreversible and I confirm that I want to proceed with the complete deletion of this pull request's data.
Thank you for your prompt attention to this critical security matter.
Best regards,
Arthur Horeanu
Beta Was this translation helpful? Give feedback.
All reactions