TDD＆Git commit comments

Question

我在我的项目中使用了TDD。
我写了一个测试，看它失败，编写代码让它变绿并且使用Git。
我已阅读关于提交第一次开发的内容，但我不明白如何使用此工作流程执行此操作。
如果我正在测试一个应用程序层（如Service或Repository），我应该在提交中写什么样的评论，以便让其他人看起来更好？
我应该写测试的名字吗？ 你是如何处理这个问题的？

Answer 1

提交TDD更改应该与任何其他更改没有区别。因此，您对提交消息应用相同的规则。

这里的an example from tpope：

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