正确提交消息 [英] Proper Commit Messages

问题描述

提交消息有什么用？我一直在写这些书来解释自己的所作所为，但最近我与一位同事进行了讨论，后者写了提交消息解释自己的所作所为。

What are commit messages for? I've always been writing them as an explanation of what I did, but I've recently gotten into a discussion about it with a colleague who writes commit messages explaining why he did. Which one is right, or is there another answer entirely?

注意：我绝对不知道是否有正确的答案。因此，我已将其标记为社区Wiki，并且不会接受答案。投票者应决定获胜者：）

NOTE: I have absolutely no idea if there is a "right" answer for this. As such, I've labeled it community wiki and will not accept an answer. Upvotes shall decide the winner :)

推荐答案

作为个人喜好，我可以告诉做什么直接查看文件中的差异。 为什么是我无法从实际变化中得出的结论。

As a personal preference, I can tell what was done by looking at the differences in the files directly. The why is the thing I can't infer from just looking at the actual changes.

如果变化很大或很复杂，那么我
不仅包括原因，还包括 how 的简要概述。

If the changes are significant or complicated, then I would include not only the why, but also a brief overview of the how.

这篇关于正确提交消息的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！