Commit Messages Rule

[brighthonor]

Commit messages rule에 대해서 건의합니다.

앞으로 commit 시에 Semantic Commit Messages 를 사용하는 걸 추천합니다.

References:

• https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716

Format: <type>(<scope>): <subject>

<scope> is optional

Example

• feat: (new feature for the user, not a new feature for build script)
• fix: (bug fix for the user, not a fix to a build script)
• docs: (changes to the documentation)
• style: (formatting, missing semi colons, etc; no production code change)
• refactor: (refactoring production code, eg. renaming a variable)
• test: (adding missing tests, refactoring tests; no production code change)
• chore: (updating grunt tasks etc; no production code change)