Thank you for improving Open Code Review Toolkit. Keep changes focused, add regression tests for behavior changes, and use synthetic examples only.
Participation in this project is governed by the Code of Conduct. Report conduct incidents through its private enforcement route rather than a public issue.
- Create a branch from
main. - Install the locked development environment with
uv sync --frozen. - Update
PLANS.mdfor substantial work. - Add a Towncrier fragment for user-visible changes.
- Run the checks in docs/development.md.
- Open a pull request; protected
mainaccepts changes only through green pull requests.
Every non-release merge publishes a development build for the current .next-version line to TestPyPI. Stable releases use a repository-owned release/vX.Y.Z branch and an exact Release vX.Y.Z pull-request title; merging that reviewed PR authorizes the automated TestPyPI, PyPI, and GitHub Release chain.
Do not include real credentials, provider payloads, internal hosts, or private repository details. Security reports should follow SECURITY.md, while conduct incidents follow CODE_OF_CONDUCT.md; neither belongs in a public issue.