From 9f2ec79d67be41211f2f110ddc2e3e45bca8c6db Mon Sep 17 00:00:00 2001 From: Pierre Vanduynslager Date: Wed, 9 Oct 2019 16:31:00 -0400 Subject: [PATCH] docs: limit list of suggested tools for commit linting --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9220f12f84..a5a1049dd8 100644 --- a/README.md +++ b/README.md @@ -52,7 +52,7 @@ This removes the immediate connection between human emotions and version numbers By default **semantic-release** uses [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines). The commit message format can be changed with the [`preset` or `config` options](docs/usage/configuration.md#options) of the [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer#options) and [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator#options) plugins. -Tools such as [commitizen](https://github.com/commitizen/cz-cli), [commitlint](https://github.com/conventional-changelog/commitlint) or [semantic-git-commit-cli](https://github.com/JPeer264/node-semantic-git-commit-cli) can be used to help contributors and enforce valid commit messages. +Tools such as [commitizen](https://github.com/commitizen/cz-cli) or [commitlint](https://github.com/conventional-changelog/commitlint) can be used to help contributors and enforce valid commit messages. Here is an example of the release type that will be done based on a commit messages: