Skip to content

docs(AGENTS): local gate is the merge gate; main requires no status checks #662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ScriptedAlchemy merged 1 commit into from
Sep 6, 2026
Merged

docs(AGENTS): local gate is the merge gate; main requires no status checks #662

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,10 +196,16 @@
after each push until none remain. Only then merge.
- PRs are squash-merged. Review threads left on an already-merged PR must
still be answered, in a follow-up PR.
- `main` is protected: PRs land only with every required check green
(`gh pr merge --squash --auto`; `gh pr update-branch` only when GitHub
reports the branch as conflicting — up-to-date-ness is not enforced, and
CI runs again on `main` after the merge); never bypass with `--admin`.
- `main` requires no status checks (owner decision, 2026-09-06): the local
gate is the merge gate. Before `gh pr merge --squash`, run on a branch that
contains current `origin/main`: `pnpm build && pnpm typecheck && pnpm lint
&& pnpm test:unit`, every integration/packed test file the diff touches,
and `pnpm docs:site:build` when `website/` or public exports changed;
paste the commands and their results in the PR body. Do not wait for CI on
the PR. CI still runs on `main` after the merge: whoever merged watches
that run and fixes or reverts a red `main` before starting anything else.
`gh pr update-branch` only when GitHub reports the branch as conflicting;
never `--admin`, never force-push `main`.

## Vendored repos

Expand Down
Loading