每次 git commit 的 message（英文）的末尾是否需要英文的句号呢？

[Livid]

其实这是我自从开始用版本控制系统就一直纠结的一个问题。

[yangqi]

这个真的不重要，跟着你的感觉走，实在不行就掷硬币

[jjgod]

message 不加，description 要加。

[lightening]

不需要。我的 commit message 不是完整的句子。（一般缺主语）

[aveline]

一般不加，看個人習慣吧。

我一般是這麼寫 Commit Message 的，不知道其他人怎麼寫。。。

[thedevil5032]

果断加，丢不掉的强迫症，哈哈。

[wwqgtxx]

从来不加

[jianghu52]

我自己用的git版本都是写中文的。

[alexrezit]

我都加了.

[hustlzp]

不加

[013231]

如果message是個完整的句子就加句號, 不是就不加.

[wy315700]

@jianghu52 中文+1 看得懂最重要

[rrrrutdk]

把Git Commit Message当成一封邮件看待，首行为标题。

[raptor]

不加

[Keyes]

<改动类型>：<详细说明>

改动类型：新功能、功能增强、BUG-FIX等
详细说明：字面意思

一句话无标点不加句号
一句话以上加句号

[toctan]

DO

- Write the summary line and description of what you have done in the imperative mode, that is as if you were commanding someone. Write “fix”, “add”, “change” instead of “fixed”, “added”, “changed”.
- Always leave the second line blank.
- Line break the commit message (to make the commit message readable without having to scroll horizontally in gitk).

DON’T

- Don’t end the summary line with a period.

https://github.com/erlang/otp/wiki/Writing-good-commit-messages
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

[dalang]

@aveline 请问截图的软件叫什么名字？

[NemoAlex]

@dalang 这个目测是用QQ截的

[dalang]

@NemoAlex
@aveline
抱歉问得有点歧义了，我是问截图里的git客户端软件叫什么名字？

[toctan]

@Keyes 更加适当的格式：

Capitalized, short (50 chars or less) summary

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body. The blank
line separating the summary from the body is critical (unless you omit
the body entirely); tools like rebase can get confused if you run the
two together.

Write your commit message in the imperative: "Fix bug" and not "Fixed bug"
or "Fixes bug." This convention matches up with commit messages generated
by commands like git merge and git revert.

Further paragraphs come after blank lines.

- Bullet points are okay, too

- Typically a hyphen or asterisk is used for the bullet, preceded by a
single space, with blank lines in between, but conventions vary here

- Use a hanging indent

http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html

[NemoAlex]

@dalang http://www.sourcetreeapp.com/
OS X 平台最棒的免费 Git/Mercurial GUI 工具