Marc Billow
61f13e7484
One commit per issue/logical change, and every commit's author and committer must be the human accountable for the work -- never a tool, bot, or AI agent identity, and no AI co-author trailers. AGENTS.md points any AI coding agent working here back to CONTRIBUTING.md as the authoritative source for this.
29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
# Contributing
|
|
|
|
See the README's [Contributing](README.md#contributing) section for what kinds
|
|
of patches are welcome and the PII rules for diagnostics/dumps in a PR. This
|
|
file covers how changes get committed.
|
|
|
|
## Commits
|
|
|
|
- **One commit per issue or logical change.** Don't bundle unrelated fixes
|
|
into a single commit, even when working through a batch of issues in one
|
|
sitting — each issue gets its own commit (and its own PR, unless there's a
|
|
specific reason to combine them).
|
|
- **Author and committer must be the human accountable for the change** —
|
|
never a tool, bot, or AI agent identity — including when the change was
|
|
drafted or applied by an AI coding agent. Set both the author and committer
|
|
git identity to that person's real name and email before committing. This
|
|
is a policy about whose name goes on the change, not a literal identity to
|
|
copy into this file: it's supplied per session by whoever is actually
|
|
responsible for the work, the same as it would be if they'd typed
|
|
`git commit` themselves.
|
|
- **No co-author trailers for AI tools or assistants.** Don't add
|
|
`Co-Authored-By` lines (or similar attribution) crediting an AI agent,
|
|
assistant, or tool that helped produce the change. The commit is
|
|
attributed entirely to the accountable human.
|
|
|
|
## For AI coding agents
|
|
|
|
See `AGENTS.md`.
|