|
1 | 1 |
|
2 | | -# ------------------------ >8 ------------------------ |
3 | | -|<---- Using a Maximum Of 50 Characters ---->| Hard limit to 72 -->| |
4 | | -<type>: <subject> |
5 | | - |
6 | | -<description> |
7 | | - |
8 | | -fixes #<issue> |
9 | | - |
10 | | ----------------------------------------------------- |
11 | | - |
12 | | -<type> can be |
13 | | - feat (new feature) |
14 | | - fix (bug fix) |
15 | | - docs (documentation only) |
16 | | - refactor (refactoring production code) |
17 | | - style (formatting, missing semicolons, etc. no code change) |
18 | | - test (adding or refactoring tests; no production code change) |
19 | | - chore (updating npm scripts etc. no production code change) |
20 | | - revert (revert a commit |
21 | | - <subject> must be the reverted commit's title |
22 | | - <description> must contain "This reverts commit <hash>.") |
23 | | - |
24 | | -Remember to |
25 | | - Not capitalize the subject line |
26 | | - Use the imperative mood in the subject line |
27 | | - Do not end the subject line with a period |
28 | | - Separate subject from body with a blank line (comments don't count) |
29 | | - Use the body to explain what and why vs. how |
30 | | - |
31 | | -If you can't summarize your changes in a single line, they should |
32 | | -probably be split into multiple commits |
| 2 | +# |<---- Using a Maximum Of 50 Characters ---->| Hard limit to 72 -->| |
| 3 | +# <type>: <subject> |
| 4 | +# |
| 5 | +# <description> |
| 6 | +# |
| 7 | +# fixes #<issue> |
| 8 | +# |
| 9 | +# ---------------------------------------------------- |
| 10 | +# |
| 11 | +# <type> can be |
| 12 | +# feat (new feature) |
| 13 | +# fix (bug fix) |
| 14 | +# docs (documentation only) |
| 15 | +# refactor (refactoring production code) |
| 16 | +# style (formatting, missing semicolons, etc. no code change) |
| 17 | +# test (adding or refactoring tests; no production code change) |
| 18 | +# chore (updating npm scripts etc. no production code change) |
| 19 | +# revert (revert a commit |
| 20 | +# <subject> must be the reverted commit's title |
| 21 | +# <description> must contain "This reverts commit <hash>.") |
| 22 | +# |
| 23 | +# Remember to |
| 24 | +# Not capitalize the subject line |
| 25 | +# Use the imperative mood in the subject line |
| 26 | +# Do not end the subject line with a period |
| 27 | +# Separate subject from body with a blank line (comments don't count) |
| 28 | +# Use the body to explain what and why vs. how |
| 29 | +# |
| 30 | +# If you can't summarize your changes in a single line, they should |
| 31 | +# probably be split into multiple commits |
0 commit comments