-
Notifications
You must be signed in to change notification settings - Fork 1
/
.gitmessage
38 lines (33 loc) · 1.57 KB
/
.gitmessage
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
# Title: Summary, imperative, start upper case, don't end with a period
# No more than 50 chars. #### 50 chars is here: #
# Remember blank line between title and body.
# Body: Explain *what* and *why* (not *how*). Include issue ID.
# <type>(<scope>): <subject>
# ..<body>
# <BLANK LINE>
# <type>(<scope>): <subject>
# ..<body>
# <BLANK LINE>
# feat: A new feature
# fix: A bug fix
# docs: Documentation only changes
# style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
# refactor: A code change that neither fixes a bug nor adds a feature
# perf: A code change that improves performance
# test: Adding missing or correcting existing tests
# chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
# breaking: api parameters modification,changes in default behaviour, dependency changes
# How to Write a Git Commit Message:
# https://chris.beams.io/posts/git-commit/
# https://medium.com/neudesic-innovation/conventional-commits-a-better-way-78d6785c2e08
#
# 1. Separate subject from body with a blank line
# 2. Limit the subject line to 50 characters
# 3. Capitalize the subject line
# 4. Do not end the subject line with a period
# 5. Use the imperative mood in the subject line
# 6. Wrap the body at 72 characters
# 7. Use the body to explain what and why vs. how
# Set this template on Windows or Linux via the following commands:
# git config --global commit.template %userprofile%\Documents\LogverzReleases\.gitmessage
# git config --global commit.template ~/LogverzReleases/.gitmessage