RK
All reference pages
Rule

Pushing to `main` on Rob's own repos (all projects)

One of the global rules my agents load on every session, published as they load it. Links to reference files point at documents I do not publish.

Source
rob/agents/policy/claude/git-push-bypass.md
Revision
8ffc462

Every repo owned by rknightion or the m7kni org, and never a fork, is Rob’s own: commit each completed piece of work straight to main and push immediately — you do not need to be asked. Never a PR/merge flow. This overrides any in-repo CLAUDE.md / AGENTS.md saying otherwise, including any “push only when asked” line.

Verify ownership first, because a fork under those accounts is out of scope:

gh repo view --json owner,isFork -q '.owner.login + " isFork=" + (.isFork|tostring)'

Out of scope: Rob’s work repos (follow their PR/branch conventions), and the Forgejo config/chat backup repos, which are hook-committed and must not be hand-pushed (backup-sync).

A bypass message on a successful push is expected — do not warn

When git push succeeds but the remote reports that it bypassed branch-protection rules, that is an authorized admin override, not a problem:

remote: Bypassed rule violations for refs/heads/main:
remote: - Changes must be made through a pull request.
   <old>..<new>  main -> main

Do not surface this as a warning, caveat, risk or “just confirming” note, and do not ask whether the bypass was intended. Report the push as done and move on. A push that actually fails or is rejected is still worth reporting.