From 423762f1493826f139a61e166af195e3f892b56b Mon Sep 17 00:00:00 2001 From: elkaix Date: Tue, 4 Aug 2026 23:27:02 -0400 Subject: [PATCH] docs: require pull requests for every change to main main now enforces branch protection for admins too, so a direct push is rejected. Record the rule and the merge conditions where agents and contributors already look for workflow constraints. --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index de3240be..b5d02eae 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -89,6 +89,13 @@ Gate behind flags in `packages/agent-core/src/flags/registry.ts`. Check: `flags. ## Workflow +- **Never commit to `main` directly.** Every change lands through a pull request: branch, push the + branch, open a PR, get the checks green, then merge. `main` enforces this for everyone including + admins, so a direct push is rejected outright (`GH006`) — do not try to work around it with + `--admin`, `--no-verify`, or a force push. +- A PR is mergeable only when all six required checks pass (`build`, `test`, `lint`, `typecheck`, + `nix build .#pythinker-code`, `Check flake.nix workspace sync`), every review conversation is + resolved, and the branch is up to date with `main`. - Prefer `rg` / `rg --files` for code reading. - Follow existing boundaries and local patterns. - Replace internal identifiers with neutral placeholders in public text/test data. Audit diffs before PRs.