Skip to content

docs: Read contribution policy from the current PR target #154

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
BenWestgate merged 1 commit into from
Oct 20, 2026
Merged

docs: Read contribution policy from the current PR target #154

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
15 changes: 10 additions & 5 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,11 +86,16 @@ Resolve scope questions from the changed code and the invariants first. Ask only
if a material security decision remains unclear; identify the decision rather
than stopping on general uncertainty. Ask before running a recommended security review.

Follow `docs/developer/AI_POLICY.md` for contributions and `SECURITY.md` for
private vulnerability reporting. Local edits, checks, and atomic commits are
allowed; do not automatically push, open pull requests, write replies, contact
maintainers, or claim authorship. A human publishes contributions. Never commit
to master or push to an open pull request branch without explicit user direction.
Before acting on a pull request, read `CONTRIBUTING.md` and
`docs/developer/AI_POLICY.md` from its current target branch. Follow that merged
contribution policy when the topic branch contains an older version. AI may
write PR descriptions and review replies under the tool-neutral policy.

Follow `SECURITY.md` for private vulnerability reporting. Local edits, checks,
and atomic commits are allowed. Publish only within the user's authorized scope;
permission to use AI does not itself authorize contacting others. Never claim
independent human authorship, commit to master, or push to an open pull request
branch without explicit user direction.

When asked to commit, keep commits focused and independently passing unless the
user explicitly requests a combined commit. Use an imperative subject of at
Expand Down
Loading