From 61762e67a0130ba829d121f297931205138ad363 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Mon, 1 Apr 2019 11:46:14 +0100 Subject: [PATCH] docs: update commitlint URL The current commitlint URL goes to a repo which contains a redirect message and new URL. Replace the outdated URL with the new URL for the commitlint repo. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ee9f35bd..c8cad592 100644 --- a/README.md +++ b/README.md @@ -57,7 +57,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/marionebl/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), [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. Here is an example of the release type that will be done based on a commit messages: