Contributions may use AI assistance, but the submitter remains responsible for correctness, security, testing, and understanding the change.
Start a change
- Read the repository rules and the guide for the code or documentation surface you will change.
- Bootstrap repo-managed tools and verify the workstation before editing.
- Choose the smallest test depth that proves the behavior, then expand with the risk.
- Keep generated artifacts synchronized and review every generated diff.
- Use a scoped conventional commit and hand CI evidence to the reviewer.
verify
PR-equivalent local gate
devenv test
devenv tasks run operator:bootstrap
devenv tasks run operator:doctor
devenv tasks run operator:ci-coreContributor routes
Set up a workstation
Bootstrap tools and choose a local development loop.
Follow project standardsApply the Go, controller, security, documentation, and generated-file rules.
Test a changeChoose unit, integration, E2E, fuzz, performance, or platform validation.
Run CI-equivalent checksMap local evidence to pull-request and scheduled workflows.
Protect the supply chainReview dependency, provenance, distribution, and governance controls.
Prepare a releaseBuild once, promote by digest, publish, and retain evidence.
Respond to a publishing incidentContain, investigate, rotate trust, and recover release automation.