forked from ibm-developer/generator-ibm-service-enablement
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.gittemplate
20 lines (18 loc) · 903 Bytes
/
.gittemplate
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
# Type(<scope>): <subject>
# <body>
# <footer>
# Type should be one of the following:
# * BREAKING CHANGES (breaking change) [major release -- 1.x.x]
# * feat (new feature) [minor release -- x.1.x]
# * fix (bug fix) [patch release -- 0.0.x]
# * 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 is just the scope of the change. Something like (admin) or (teacher).
# Subject should use clear words and say what you did.
# The body should go into detail about changes made.
# The footer should contain any Github (or other tool) issue references or actions.
# For a full example of how to write a good commit message, check out
# https://conventionalcommits.org/