讨论： Describing a change so that reviewers can review it

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

暂无译文，显示原文。 原文

Elaborate descriptions duplicate what should be in the commit messages and the code. If commits are well written, the description is their concatenation; if they are not, the description compensates for a problem that will still exist in the history after merge. I would rather invest the effort in the commits, as the commit-message article argues, and keep the description to the review guidance.