Skip to content

ikngtty/emoji_prefix_of_commit_message

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

2 Commits
Β 
Β 

Repository files navigation

Emoji Prefix of Commit Message

Emoji Emoji String Meaning Subject of Commit Counterpart in Conventional Commits
🎢 :notes: improve behavior or API Major update (*1) BREAKING CHANGE:
✨ :sparkles: implement a new function or the first commit Minor update (*1) feat:
πŸ› :bug: fix a bug Patch update (*1) fix:
🐴 :horse: improve performance Non-functional feature (*2) perf:
πŸ”’ :lock: improve security Non-functional feature (*2) feat:(?)
πŸ” :mag: about test codes Maintenability test:
πŸ“ :memo: about documentation (*3) Maintenability docs:
πŸ’š :green_heart: refactor Maintenability refactor: or style:
⬆️ :arrow_up: update dependencies (includes code changes for it) Maintenability chore:
πŸ”§ :wrench: configure for development or CI tools Maintenability chore:
πŸ”– :bookmark: about a release Release chore:
πŸš€ :rocket: about a deploy Deploy chore:
🚧 :construction: WIP (work in progress) Temporary none

(*1) By the semantic versioning
(*2) These may belong to minor update.
(*3) Including comments in source code. Their role is just a document, and they may be used by document generators.

Why do you use a GitHub repository, not Gist?

Because I want to record commit messages, descriptions of reason for change.

About

My rule template of an emoji prefix of a commit message.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published