V2EX = way to explore
V2EX 是一个关于分享和探索的地方
Sign Up Now
For Existing Member Sign In
This topic created in 4638 days ago, the information mentioned may be changed or developed.
其实这是我自从开始用版本控制系统就一直纠结的一个问题。
 |
1
yangqi Aug 27, 2013
这个真的不重要，跟着你的感觉走，实在不行就掷硬币
|
 |
2
jjgod Aug 27, 2013  1
message 不加，description 要加。
|
 |
3
lightening Aug 27, 2013 1
不需要。我的 commit message 不是完整的句子。（一般缺主语）
|
 |
4
aveline Aug 27, 2013
一般不加，看個人習慣吧。
我一般是這麼寫 Commit Message 的，不知道其他人怎麼寫。。。  |
 |
5
thedevil5032 Aug 27, 2013 via iPad
果断加，丢不掉的强迫症，哈哈。
|
 |
6
wwqgtxx Aug 27, 2013 via Android
从来不加
|
 |
7
jianghu52 Aug 27, 2013
我自己用的git版本都是写中文的。
|
 |
8
alexrezit Aug 27, 2013
我都加了.
|
 |
9
hustlzp Aug 27, 2013
不加
|
 |
10
013231 Aug 27, 2013
如果message是個完整的句子就加句號, 不是就不加.
|
 |
12
rrrrutdk Aug 27, 2013 1
把Git Commit Message当成一封邮件看待，首行为标题。
|
 |
13
raptor Aug 27, 2013
不加
|
 |
14
Keyes Aug 27, 2013
<改动类型>：<详细说明>
改动类型：新功能、功能增强、BUG-FIX等 详细说明：字面意思 一句话无标点不加句号 一句话以上加句号 |
 |
15
toctan Aug 27, 2013 1
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 |
|
19
toctan Aug 27, 2013
@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 |
 |
20
NemoAlex Aug 27, 2013
|
 |
21
CoX Aug 27, 2013
我个人习惯是写上bug号~~
 |
 |
25
ssword Aug 27, 2013 via Android
第一句相当于标题
|
Select Language