-
Notifications
You must be signed in to change notification settings - Fork 0
/
.gitmessage
133 lines (119 loc) · 5.44 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
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
# Commit message
#------------------------------------------------|
# Subject: |
# - Separate subject from body with a blank line |
# - Limit the subject line to 50 characters |
# - Capitalize the subject line |
# - Do not end the subject line with a period |
# - Use the imperative mood in the subject line |
#------------------------------------------------|
# feat:
# fix:
# docs:
# ci:
# style:
# refactor:
# perf:
# chore:
# test:
# build:
#----------------------------------------------------------------------|
# Body: |
# - Wrap the body at 72 characters |
# - Use the body to explain what and why vs. how |
#----------------------------------------------------------------------|
# body start
# body end
#----------------------------------------------------------------------|
# Footer: |
# - One or more footers MAY be provided one blank line after the body. |
#----------------------------------------------------------------------|
# Breaking changes: |
# - A BREAKING CHANGE commit introduces a breaking API change |
# - Breaking changes MUST be indicated |
#----------------------------------------------------------------------|
# BREAKING CHANGE:
#----------------------------------------------------------------------|
# Issue Key: |
# - Connecting Jira Software to supported development tools like |
# Bitbucket, GitHub, GitLab, and others. |
# - Multiple issues have to be a issue followed by a comma or a space. |
#----------------------------------------------------------------------|
# issue:
#------------------------------ Reference ------------------------------
#----------------------------------------------------------------------|
# Format |
#----------------------------------------------------------------------|
# <type>(<scope>): <subject>
# <BLANK LINE>
# <body>
# <BLANK LINE>
# <footer>
#----------------------------------------------------------------------|
# Example |
#----------------------------------------------------------------------|
# feat: Allow provided config object to extend other configs
#
# Introduce a request id and a reference to latest request. Dismiss
# incoming responses other than from latest request.
#
# BREAKING CHANGE: `extends` key in config file is now used for
# extending other config files
#----------------------------------------------------------------------|
# Commit type |
#----------------------------------------------------------------------|
# feat: A new feature
# fix: Fixed a bug
# docs: Documentation only changes
# style: Changes to styling like white space, formatting, semi-colons
# refactor: Refactors production code, A code change that neither fixes a bug nor adds a feature (e.g. renaming a variable)
# ci: Changes made to the CI configuration like Travis, Circle, Actions
# perf: A code change that improves performance
# test: Add or fix tests; no production code change
# chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
# build: Changes that affect the build system or external dependencies (e.g. gulp, broccoli, npm)
#----------------------------------------------------------------------|
# Rules |
#----------------------------------------------------------------------|
# ==== The Seven Rules ====
# 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
#
# How to Write a Git Commit Message http://chris.beams.io/posts/git-commit/
#
# for http://memo.goodpatch.co/2016/07/beautiful-commits-with-emojis/
# Reference
# Conventional Commits 1.0.0
# https://www.conventionalcommits.org/ja/v1.0.0/
#
# AngularJS Git Commit Message Conventions
# https://gist.github.com/stephenparish/9941e89d80e2bc58a153
#
#---------------------------------
# Capitalized, short (50 chars or less) summary
#
# More detailed explanatory text, if necessary. Wrap it to about 72
# characters or so. In some contexts, the first line is treated as the
# subject of an email and the rest of the text as the body. The blank
# line separating the summary from the body is critical (unless you omit
# the body entirely); tools like rebase will confuse you if you run the
# two together.
#
# Write your commit message in the imperative: "Fix bug" and not "Fixed bug"
# or "Fixes bug." This convention matches up with commit messages generated
# by commands like git merge and git revert.
#
# Further paragraphs come after blank lines.
#
# - Bullet points are okay, too
#
# - Typically a hyphen or asterisk is used for the bullet, followed by a
# single space, with blank lines in between, but conventions vary here
#
# - Use a hanging indent
#---------------------------------