Add a comment policy to CONTRIBUTING.md #40
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/comment-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?
Problem
The codebase is over-commented and trimming has been case-by-case with no stated standard. Closes #27.
Fix
Adds a Comments section to CONTRIBUTING.md, placed right after Commits as the flip side of its principle: the commit body is the record of why, so a comment earns its place only by carrying what the code plus
git blamecannot — a non-obvious external constraint, a warning that the obvious simplification is wrong, or a deliberate deviation from the surrounding pattern.The issue proposed an explicitly AI-binding clause; deliberately dropped — the policy is tool-agnostic and covers generated code by construction, matching the rest of the file (which names no authoring tools anywhere).
Second commit applies the policy across the codebase, starting from the issue's model case (
restore_default_dns): deletes comments restating the code, structure labels, and commented-out code; rewords the few restaters that hid a real constraint; keeps everything naming a non-obvious constraint or warning off a wrong simplification. Comment-only diff, verified by filtering changed lines.Verification
python -m py_compile aqomui/aqomui_service.pypasses; the code change is comment-only, no behavior change.2c9530c975to449aa79ded