Add a comment policy to CONTRIBUTING.md #27
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The codebase is over-commented, including by AI assistance, and it needs
a stated standard rather than repeated case-by-case trimming.
The distinction to encode: the durable record of why belongs in commit
messages, which CONTRIBUTING.md already says well. So comments are rare and
reserved for what a reader cannot recover from the code plus
git blame.Proposed shape -- write a comment only when it names a non-obvious external
constraint, warns that an obvious simplification is wrong, or explains a
deliberate deviation from the surrounding pattern. Never to restate code,
narrate the change's history, or label structure. Prefer a clearer name or a
smaller function over a comment explaining a confusing one.
Include the clause making this explicitly binding on AI-generated commentary,
since that is the stated source of the drift.
restore_default_dns(aqomui_service.py:288-294) is the model case: acommit-message paragraph living in the source, where the content is already in
the commit body.