Guidelines
- Seperate subject from body with a blank line
- Do not end the subject liine with a period
- Capitalize the subject line and each paragraph
- Use the imperative mood in the subject line
- Wrap lines at 72 characters
- Use the body to explain what and why you have done something rather than how.
Summary
<subject line> : capitalized imperative short summary
<body> : focused on what and why
<footer> : if you have specific issue number or ticket
Tips
-
Use type on subject line if you want:
- feat - a new feature
- fix - a bug fix
- docs - changes in documentation
- style - everything related to styling
- refactor - code changes that neither fixes a bug or adds a feature
- test - everything related to testing
- chore - updating build tasks, package manager configs, etc
-
Use bullet points on body paragraph - I prefer this
-
Put references on footer if you use an issue tracker:
Resolves: #123
See also: #456, #789
References
[Git] 좋은 커밋 메세지 작성하기위한 규칙들
Commit message guidelines
How To Write Proper Git Commit Messages