docs: clarify implementation commit-history policy (#40) #41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-40-commit-policy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Refs #40. Clarifies only
.kilo/rules/30-implementation-discipline.mdand.kilo/command/implement-issue.md: commit count is not an acceptance criterion; use as many small, coherent, reviewable commits as needed; remediation commits are normal; do not squash, amend, force-push, or rewrite published history merely to reduce commit count. Overall scope remains focused and coherent.No product/runtime, AGit, routing/reviewer, dependency, or single-issue/PR semantics changed.
Evidence
eb2bcceeafaf1dccc6f6cfba3d456d529eaa0baabcd30e779d0eaaf5595df2116eac3c892b09ae29make check: passed; locked dependencies, Ruff format/lint, basedpyright (0 errors/warnings), import boundary, 869 tests, secret scan and whitespace checks.make package-check: passed; wheel metadata/license, sdist rebuild, isolated install and CLI replay/export.git diff --check eb2bcceeafaf1dccc6f6cfba3d456d529eaa0baa HEADand staged whitespace check: passed.make auditnot run: documentation-only change, no dependency/tooling changes.Ready for review, not independently reviewed or approved. No reviewer sessions, merge, history rewriting, release or deployment performed. Issue remains open. No unresolved blockers.
kilo referenced this pull request from Creatidy/model-intelligence2026-10-01 00:34:01 +00:00