angular-cn/tools/validate-commit-message/spec/support/jasmine.json

{
  "spec_dir": "",
  "spec_files": [
    "**/*[sS]pec.js"
  ],
  "helpers": [
    "helpers/**/*.js"
  ],
  "stopSpecOnExpectationFailure": false,
  "random": false
}
ci: validate the message of each new commit as part of the CI linting This patch adds the gulp command of `validate-commit-messages` which will validate the range of commits messages present in the active branch. This check now runs on CI as part of the linting checks. Allowed commit message types and scopes are controlled via commit-message.json file and documented at https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines This solution is based on old Vojta's code that he wrote for angular/angular.js, that was later adjusted by @matsko in #13815. Ideally we should switch over to something like https://www.npmjs.com/package/commitplease as suggested in #9953 but that package currently doesn't support strict scope checking, which is one of the primarily goal of this PR. Note that this PR removes support for "chore" which was previously overused by everyone on the team. Closes #13815 Fixes #3337 2017-01-19 19:24:47 -05:00			`{`
			`"spec_dir": "",`
			`"spec_files": [`
			`"*/[sS]pec.js"`
			`],`
			`"helpers": [`
			`"helpers/*/.js"`
			`],`
			`"stopSpecOnExpectationFailure": false,`
			`"random": false`
			`}`