tslint-config-travix - npm Package Compare versions

Comparing version 0.0.25 to 0.0.26

package.json

		{
		"name": "tslint-config-travix",
		"version": "0.0.25",
		"version": "0.0.26",
		"description": "TSLint configuration from Travix",
		@@ -28,6 +28,11 @@ "main": "index.js",
		"semantic-release": "~15.9.8",
		"simple-commit-message": "~4.0.3",
		"tslint": "~5.11.0",
		"tslint-config-prettier": "~1.14.0",
		"tslint-react": "~3.6.0"
		},
		"release": {
		"noCi": false,
		"analyzeCommits": "simple-commit-message"
		}
		}

README.md

		@@ -15,2 +15,15 @@ # tslint-config-travix
		}
		```
		```

		## Release
		Release of a new version of the npm module is triggering automatically on push (merge) to `master` branch.

		* In case you make `git push` to `master` branch it will check your commit's message to match the pattern to get release version.
		* If you merge a PR to `master` branch without squash it will check all commits one by one.
		* If you merge a PR with squash you have to handle it manually (check all commits messages and add appropriate squash message).

		### Pattern for commit messages
		We use [simple-commit-message](https://github.com/bahmutov/simple-commit-message) to simplify commit messages. Here is a pattern:
		* `fix: <MESSAGE>` - does release `patch` version of NPM module. Alias - `patch: <MESSAGE>`
		* `minor: <MESSAGE>` - releases `minor` version. Alias - `feat: <MESSAGE>`
		* `major: <MESSAGE>` - releases `major` version. Alias - `break: <MESSAGE>`

.releaserc

New alerts