GIT022

Error

Pushing to the origin remote in a Kong organization repository. Organization policy requires pushing to upstream instead.

Why this matters

In fork-based workflows, origin points to the personal fork while upstream points to the organization repository. Pushing to the wrong remote can create confusion and bypass branch protection rules.

How to fix

Push to upstream instead of origin:

# Instead of:
git push origin main

# Use:
git push upstream main

Check your remotes:

git remote -v

Configuration

This is enforced through the push validator's blocked remotes configuration:

[validators.git.push]
blocked_remotes = ["origin"]
allowed_remote_priority = ["upstream"]

Hook output

When this error is triggered, klaudiush writes JSON to stdout:

permissionDecisionReason (shown to Claude): [GIT022] Push to 'origin' is blocked. Push to 'upstream' remote instead: git push upstream <branch>

systemMessage (shown to user): Formatted error with fix hint and reference URL.

additionalContext (behavioral guidance): Automated klaudiush validation check. Fix the reported errors and retry the same command.

Related

• GIT007 - missing remote for push
• GIT025 - push to blocked remote