From 5b8a93ed90808fc0b9788a92e616b26ff2e956ac Mon Sep 17 00:00:00 2001 From: Homa Wong Date: Sat, 11 Nov 2017 03:47:17 -0800 Subject: [PATCH] docs: Callout "Others" commit type Merge from unional/unional-patch-1 --- index.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/index.md b/index.md index 6c35905..e38f557 100644 --- a/index.md +++ b/index.md @@ -32,14 +32,11 @@ consumers of your library: with [`MINOR`](http://semver.org/#summary) in semantic versioning). 3. **BREAKING CHANGE:** a commit that has the text `BREAKING CHANGE:` at the beginning of its optional body or footer section introduces a breaking API change (correlating with [`Major`](http://semver.org/#summary) in semantic versioning). A breaking change can be part of commits of any _type_. e.g., a `fix:`, `feat:` & `chore:` types would all be valid, in addition to any other _type_. - +4. Others: commit _types_ other than `fix:` and `feat:` are allowed, for example [the Angular convention](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit) recommends `docs:`, `style:`, `refactor:`, `perf:`, `test:`, `chore:`, but these tags are not mandated by the conventional commits specification.
A scope may be provided to a commit's type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`. -Commit _types_ other than `fix:` and `feat:` are allowed, for example [the Angular convention](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit) recommends `docs:`, `style:`, `refactor:`, `perf:`, `test:`, `chore:`, but these tags are -not mandated by the conventional commits specification. - ## Introduction In software development, it's been my experience that bugs are most often introduced