들쭉날쭉한 커밋로그. 어떻게 해야 통일성 있게 작성할 수 있을까?
Udacity Commit Message Style Guide을 간략하게 번역 후 정리했다.
분류 : 제목
커밋의 주제와 부합하는 항목을 아래의 카테고리에서 하나를 고른다.
feat: Summarize changes in around 50 characters or less
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 the commit 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); various tools like
rebase can get confused if you run the two together.
Explain the problem that this commit is solving. Focus on why you
are making this change as opposed to how (the code explains that).
Are there side effects or other unintuitive consequences of this
change? Here's the place to explain them.
Further paragraphs come after blank lines.
If you use an issue tracker, put references to them at the bottom,
See also: #456, #789