Skip to content

docs: require pull requests for every change to main #19

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
elkaix merged 1 commit into from
Aug 5, 2026
Merged

docs: require pull requests for every change to main #19

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
7 changes: 7 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading