GitHub Push Protection appears when GitHub detects a secret, API key, token, or private credential inside your commit.
This often happens when you accidentally commit files like:
.env- Firebase config files
- API service files
- private keys
- access tokens
In this guide, I’ll show the simple steps I used to fix it.
Why this error happens
GitHub blocks the push because it found sensitive data inside your commit history.
Example:
bash
remote: error: GH013: Repository rule violations found
remote: Push cannot contain secrets