- 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)
https://www.conventionalcommits.org/
/en
www.conventionalcommits.org
https://seesparkbox.com/foundry/semantic_commit_messages
Semantic Commit Messages
See how a minor change to your Git commit message style can make you a better programmer.
seesparkbox.com
http://karma-runner.github.io/1.0/dev/git-commit-msg.html
Karma - Git Commit Msg
The reasons for these conventions: automatic generating of the changelog simple navigation through git history (e.g. ignoring style changes) Format of the commit message: ( ): Example commit message: fix(middleware): ensure Range headers adhere more closel
karma-runner.github.io
https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716
Semantic Commit Messages
Semantic Commit Messages. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
'협업 > git' 카테고리의 다른 글
| 쓸데없는 폴더가 포함되었을 때 제거방법 (0) | 2020.04.30 |
|---|---|
| [Gitlab] git push -u origin master permission denied (0) | 2020.04.28 |
| git bash 터미널 계정 변경 (0) | 2020.04.27 |
| GitLab 설치 후 502 GitLab is taking too much time to respond (0) | 2020.02.21 |
| GIT 설치 오류 (0) | 2020.02.21 |
