Skip to content

Commit Convention

KIM CHAN HEE edited this page Feb 20, 2023 · 1 revision

Commit Message Format

All Commit Message Format MUST meet this Text Format:

[:<Emoji>:][<Type>[(<Scope>)]:] <Message>
(Optional)[<BLANK LINE>]
(Optional)[<Message Body>]
(Optional)[<BLANK LINE>]
(Optional)[<Message Footer>]

Types

Type Description
new for new feature implementing commit
feature for new feature implementing commit (equal new)
update for update commit
bug for bug fix commit
security for security issue fix commit
performance for performance issue fix commit
improvement for backwards-compatible enhancement commit
breaking for backwards-incompatible enhancement commit
deprecated for deprecated feature commit
i18n for i18n (internationalization) commit
a11y for a11y (accessibility) commit
refactor for refactoring commit
docs for documentation commit
example for example code commit
test for testing commit
deps for dependencies upgrading or downgrading commit
config for configuration commit
build for packaging or bundling commit
release for publishing commit
wip for work in progress commit
chore for other operations commit

If the prefix is the below types, it will appear in the changelog.

  • new (feature)
  • bug
  • performance
  • security
  • improvement
  • deprecated
  • breaking

Scope

The scope could be anything specifying place or category of the commit change. For example $location, $browser, $compile, $rootScope, ngHref, ngClick, ngView, feature1, etc...

Subject

The subject contains succinct description of the change:

  • use the imperative, present tense: "change" not "changed" nor "changes"
  • don't capitalize first letter
  • no dot (.) at the end

Emojis

Emoji Raw Emoji Code Type Description
⭐ :star: new or feature add new feature
πŸ› :bug: bug fix bug issue
πŸš‘ :ambulance: bug critical hotfix bug issue
πŸ”’ :lock: security fix security issue
πŸ“ˆ :chart_with_upwards_trend: performance fix performance issue
⚑ :zap: improvement update backwards-compatible feature
πŸ’₯ :boom breaking update backwards-incompatible feature
⚠️ :warning: deprecated deprecate feature
🌐 :globe_with_meridians: i18n update or fix internationalization
β™Ώ :wheelchair: a11y update or fix accessibility
🚨 :rotating_light: refactor remove linter/strict/deprecation warnings
πŸ‘• :shirt: refactor refactoring or code layouting
βœ… :white_check_mark: test add tests, fix tests failur or CI building
πŸ“ :pencil: docs update documentation
©️ :copyright: docs decide or change license
🍭 :lollipop: example for example or demo codes
πŸ’„ :lipstick: update update UI/Cosmetic
πŸ†™ :up: update update other
🚚 :truck: update move or rename files, repository, ...
πŸ”€ :twisted_rightwards_arrows: update merge conflict resolution
βž• :heavy_plus_sign: update add files, dependencies, ...
βž– :heavy_minus_sign: update remove files, dependencies, ...
πŸ”› :on: update enable feature and something ...
⬆️ :arrow_up: deps upgrade dependencies
⬇️ :arrow_down: deps downgrade dependencies
πŸ“Œ :pushpin: deps pin dependencies
πŸ”§ :wrench: config update configuration
πŸ“¦ :package: build packaging or bundling or building
🐳 :whale: build Dockerfile
🐣 :hatching_chick: release initial commit
🎊 :confetti_ball: release release major version
πŸŽ‰ :tada: release release minor version
✨ :sparkles: release release patch version
πŸš€ :rocket: release deploy to production enviroment
πŸ”– :bookmark: release tagged with version label
πŸ”™ :back: revert revert commiting
🚧 :construction: wip WIP commiting

Examples

new:

:star: new(graphite): add 'graphiteWidth' option

bug fix:

:bug: fix(graphite): stop graphite breaking when width < 0.1

(Optional) Closes #28

improve performance:

:chart_with_upwards_trend: performance(graphite): remove graphiteWidth option

(Optional) The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reason.

revert:

:back: revert: new: add 'graphiteWidth' option

(Optional) This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
Clone this wiki locally