<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
feat: new feature
fix(scope): bug in scope
feat!: breaking change`
feat(api)!: rework API
chore(deps): update dependencies
feat
: a new feature, correlates withMINOR
in SemVerfix
: a bug fix, correlates withPATCH
chore
: changes not related to the source code or tests (e.g. build process, auxiliary tools, libraries)build
: changes that affect the build system or external dependencies (eg.gulp
,webpack
,npm
)ci
: changes to CI configuration files and scripts (e.g.travis
,circle
,browserstack
)docs
: changes related only to the documentationperf
: code change that improves performancerefactor
: generic code change that neither fixes a bug nor adds a featurerevert
: change reverting a previous editstyle
: changes that don't affect the meaning of the code (e.g. white-space, formatting, missing semi-colons)test
: adding missing tests or correcting existing ones
A commit that has a BREAKING CHANGE
footer, or appends a !
after the type and scope, introduces a breaking API change. A breaking change can be part of commits of any type and relates to MAJOR in Semantic Versioning.
Footers other than BREAKING CHANGE: <description>
may be provided and follow a convention similar to git trailer format.
feat: allow provided config object to extend other configs
BREAKING CHANGE: `extends` key in config file is now used for extending other config files
feat!: send an email to the customer when a product is shipped
feat(api)!: send an email to the customer when a product is shipped
chore!: drop support for Node 6
BREAKING CHANGE: use JavaScript features not available in Node 6.
docs: correct spelling of CHANGELOG
feat(lang): add Polish language
fix: prevent racing of requests
Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.
Remove timeouts which were used to mitigate the racing issue but are
obsolete now.
Reviewed-by: Z
Refs: #123
More details and examples at conventionalcommits.org.