25 lines
993 B
Plaintext
25 lines
993 B
Plaintext
|
# Type (<scope>): <subject>
|
||
|
|
|
||
|
|
# <body>
|
||
|
|
|
||
|
|
# <footer> (Keyword #issue)
|
||
|
|
|
||
|
|
# Type should be one of the following:
|
||
|
|
# * new (new component, file, ...)
|
||
|
|
# * del (delete component, file, ...)
|
||
|
|
# * feat (new feature)
|
||
|
|
# * fix (bug fix)
|
||
|
|
# * docs (changes to documentation)
|
||
|
|
# * style (formatting, missing semi colons, etc; no code change)
|
||
|
|
# * refactor (refactoring production code)
|
||
|
|
# * test (adding missing tests, refactoring tests; no production code change)
|
||
|
|
# * chore (updating grunt tasks etc; no production code change)
|
||
|
|
# Scope can be anything from file to component or empty (much changes)
|
||
|
|
# Subject should use imperative tone and say what you did.
|
||
|
|
# The body should go into detail about changes made.
|
||
|
|
# The footer should contain any JIRA (or other tool) issue references or actions.
|
||
|
|
# Keyword should be one of the following:
|
||
|
|
# * refs (refers to the given issue - does not fix or close it)
|
||
|
|
# * fixes (the given issue is fixed)
|
||
|
|
# * closes (the given issue is cloesd - might be new component, feature, ...)
|