협업/git

Semantic Commit Messages 정리

피고녀 2020. 3. 10. 18:02
  • 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