protect-push

To prevent direct git pushes to the main branch, you can use a PreToolUse hook to intercept push commands and block them if the branch tracks origin/main or origin/master. This enforces a Pull Request workflow for all code changes.

The best way to enforce a PR workflow in git repositories is by checking the branch tracking configuration before executing git push. Blocking direct pushes to the main branch ensures all changes go through Pull Requests, maintaining code quality and collaboration.

Branch tracking check for push protection works by verifying if the current branch is tracking origin/main or origin/master before allowing a git push. If it is, the direct push is blocked and clear instructions are provided to create a feature branch instead.

Yes, you can use git worktree and still block direct pushes to main. This push protection applies to all projects using EnterWorktree or git worktree add, requiring only proper git configuration for branch tracking and a PreToolUse hook for command interception.

Your direct pushes to origin/main are being blocked because a push protection mechanism is actively enforcing a Pull Request workflow. It checks branch tracking configuration and halts git push operations tracking origin/main or origin/master, directing you to use a feature branch.