proxybroker2/.gitmessage at master · bluet/proxybroker2 · GitHub

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
# <type>(<scope>): <subject>
#
# <body>
#
# <footer>

# Type should be one of the following:
# * feat: A new feature
# * fix: A bug fix
# * docs: Documentation only changes
# * style: Changes that do not affect the meaning of the code
# * refactor: A code change that neither fixes a bug nor adds a feature
# * perf: A code change that improves performance
# * test: Adding missing tests or correcting existing tests
# * build: Changes that affect the build system or external dependencies
# * ci: Changes to our CI configuration files and scripts
# * chore: Other changes that don't modify src or test files
# * revert: Reverts a previous commit

# Scope is optional and should be the name of the package affected
# Examples: api, server, cli, docs

# Subject should use imperative mood and not end with period
# Examples: "add proxy authentication support", "fix memory leak"

# Body should explain what and why vs. how
# Can be multiple paragraphs, each separated by a blank line

# Footer should contain any information about Breaking Changes
# and is also the place to reference GitHub issues that this commit closes
# Examples:
# BREAKING CHANGE: minimum Python version is now 3.10+
# Closes #123, #456