From d92e6762208d8f82c95d56b28c54da42034f5b97 Mon Sep 17 00:00:00 2001 From: Aori Nevo Date: Thu, 9 Apr 2020 15:57:58 -0400 Subject: [PATCH] Update README.md Co-Authored-By: Piper --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 96613d09f..81edb2ade 100644 --- a/README.md +++ b/README.md @@ -142,5 +142,5 @@ Shepherd leverages [semantic-releases](https://github.com/semantic-release/seman - Release Notes compiled via [@semantic-release/release-notes-generator](https://github.com/semantic-release/release-notes-generator) - Tagging based on commit message via [@semantic-release/commit-analyzer](https://github.com/semantic-release/commit-analyzer) - Commits that contain `BREAKING CHANGE`, `BREAKING CHANGES`, or `BREAKING` in their body will be considered breaking changes. - - Commits with a 'docs', 'style', 'refactor', or 'perf' type will be associated with a patch release + - Commits with a `'docs'`, `'style'`, `'refactor'`, or `'perf'` type will be associated with a patch release. - If a commit doesn't match any of the above rules, it will be evaluated against the [default release rules](https://github.com/semantic-release/commit-analyzer/blob/master/lib/default-release-rules.js).