Skip to content

[Security] Request to purge commit with exposed API key #12

@Eras256

Description

@Eras256

Security Request

A commit containing an exposed API key was removed from Git history, but the commit object still exists in GitHub's database.

Commit hash: \1cb03790228ae39dc12b39358728210931c5e7d1\

File: \VERCEL_ENV_SETUP.md\

Actions taken:

  • ✅ Commit removed from all branches using git filter-branch
  • ✅ History rewritten locally
  • ✅ Force push completed to remove from branch history
  • ❌ Commit object still accessible via direct hash URL

Request: Please purge this commit object from GitHub's object database.

The exposed API key has been rotated, but the commit should be completely removed from GitHub servers for security compliance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions