remote: error: GH006: Protected branch update failed / pre-receive hook declined
The server rejected your push because of branch protection rules or a server-side hook.
Protected branch update failedpre-receive hook declinedYou are not allowed to push code to protected branches Meaning
Protected branches can require pull requests, status checks, signed commits or linear history. Force pushes and direct pushes are blocked.
Common causes
- Direct push to a protected branch
- Force push blocked
- Required status checks/reviews missing
- Unsigned commits where signing is required
⚡ Quick fix
- Push to a feature branch and open a pull request
- Satisfy required checks/reviews
- Ask an admin if you truly need a bypass
Detailed fix by platform
Git
git switch -c fix/login && git push -u origin fix/login
How to diagnose
- Rule — Which protection is named in the message?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- denied denied: requested access to the resource is denied (docker push)
- GH001 large files remote: error: GH001: Large files detected. File x is 120 MB; this exceeds GitHub's file size limit of 100.00 MB
- github-actions[bot] 403 remote: Permission to owner/repo.git denied to github-actions[bot]. fatal: unable to access … The requested URL returned error: 403
Most viewed in Git
- Git SSL certificate problem fatal: unable to access 'https://…': SSL certificate problem: unable to get local issuer certificate
- unfinished merge fatal: You have not concluded your merge (MERGE_HEAD exists). Please, commit your changes before you merge.
- rebase in progress fatal: It seems that there is already a rebase-merge directory, and I wonder if you are in the middle of another rebase.
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026