protected branch 🌿 Git

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.

Seen on: Git

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

  1. Push to a feature branch and open a pull request
  2. Satisfy required checks/reviews
  3. Ask an admin if you truly need a bypass

Detailed fix by platform

Git

  1. git switch -c fix/login && git push -u origin fix/login

How to diagnose

  1. Rule — Which protection is named in the message?
  2. Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.

🧠 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.