Skip to content

fix(readme): Fix typo in config example #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 29, 2017
Merged

fix(readme): Fix typo in config example #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,7 @@ This is an `Array` of rule objects. A rule object has a `release` property and 1
{
"release": {
"analyzeCommits": {
"path": "sr-commit-analyzer",
"preset": "angular",
"releaseRules": [
{"type": "docs", "scope": "README", "release": "patch"},
Expand Down Expand Up @@ -128,6 +129,7 @@ For example with `eslint` preset:
{
"release": {
"analyzeCommits": {
"path": "sr-commit-analyzer",
"preset": "eslint",
"releaseRules": [
{"tag": "Docs", "message":"/README/", "release": "patch"},
Expand Down Expand Up @@ -178,6 +180,7 @@ The following example uses [Angular convention](https://github.com/conventional-
{
"release": {
"analyzeCommits": {
"path": "sr-commit-analyzer",
"preset": "angular",
"parserOpts": {
"noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES", "BREAKING"],
Expand Down