The ProblemYou’ve finished your work, committed your changes, and hit git push. Instead of a success message, GitHub rejects your code with a GH006 error. This usually happens when you're working on a team project where the main or master branch is under lock and key to prevent unstable code from reaching production.
remote: error: GH006: Protected branch update failed, not allowed to update the protected branch: refs/heads/main.
To github.com:username/repository.git
! [remote rejected] main -> main (protected branch hook declined)
error: failed to push some refs to 'github.com:username/repository.git'
Why This HappensGitHub uses Branch Protection Rules to keep production code stable. When these rules are active, direct pushes are blocked to prevent accidental overwrites or unreviewed bugs. If your repo has 'Require a pull request before merging' enabled, GitHub will reject any attempt to bypass the PR process. Common triggers include missing required approvals (usually 1 or 2 reviewers), failing CI/CD status checks, or a 'Restrict pushes' rule that limits access to specific senior developers.
How to Fix the Error### Method 1: The Standard Workflow (Pull Request)This is the safest path and the one your team likely expects. Instead of forcing your code into main, move it to a new feature branch and let the PR process handle the rest.
- Move your current changes to a new branch:
git checkout -b feature/fix-ui-styling- Push the new branch to the remote server:git push -u origin feature/fix-ui-styling- Start a Pull Request: Open your repository on GitHub. You’ll see a yellow bar suggesting a "Compare & pull request." Click it, describe your 2-3 key changes, and hit submit.- Merge the code: Once your teammates approve the PR and your tests pass, click Merge pull request on GitHub.- Sync your local environment:``` git checkout main git pull origin main
- Find the rule for `main` and click **Edit**.- Look for the **"Include administrators"** checkbox. If this is checked, even the owner is blocked from pushing. Uncheck it to give yourself a bypass.- Alternatively, you can uncheck **"Require a pull request before merging"** if you want to disable the protection entirely for a moment.- Scroll to the bottom, click **Save changes**, and try your push again.### Method 3: Checking the "Restrict Pushes" ListSome organizations use a whitelist to control who can push. If you're a new hire, your username might not be on that list yet. Ask your lead to check the **Restrict pushes** section in the branch protection settings and add your specific GitHub handle or your team name.
## VerificationRun your push command one more time to ensure everything is cleared:
git push origin main
A successful push will look like this:
To github.com:username/repository.git d4e5f6g..h7i8j9k main -> main
## Prevention Tips- **Adopt a "Branch First" mindset:** Run `git checkout -b [branch-name]` before you write a single line of code.- **Use Local Hooks:** Create a `pre-push` script in your `.git/hooks` folder. This script can check if your current branch is `main` and stop the push before it even leaves your computer.- **Draft PRs:** If you have 10+ commits and want early feedback without triggering a final review, use GitHub’s "Draft" mode.