iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
angular-docs-cn/tools/validate-commit-message/commit-message.json

44 lines
656 B
JSON
Raw Normal View History

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 16:24:47 -08:00
{
build: temporarily increase the commit msg limit to 120 Right now HEAD and 5.0.x have a branch deviation and therefore all the commits between both branches are being compared. There exists a problematic commit which has a commit message that is longer than 100 commits. This patch will temporarily increase the limit to 120 so that CI passes. Once master is resumed to being the primary development branch (once 5.0.0 is out) then the the msg limit will be set back to 100.
2017-10-30 15:05:35 -07:00
"maxLength": 120,
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 16:24:47 -08:00
"types": [
"build",
"ci",
"docs",
"feat",
"fix",
"perf",
"refactor",
build: add `release` as a valid commit message subject (#19955) PR Close #19955
2017-10-26 11:00:13 -07:00
"release",
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 16:24:47 -08:00
"style",
"test"
],
"scopes": [
refactor(animations): introduce @angular/animation module (#14351) PR Close: #14351
2017-01-26 11:16:51 -08:00
"animations",
docs: add 'bazel' as an Angular component (#19346)
2017-09-28 09:28:42 -07:00
"bazel",
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 16:24:47 -08:00
"benchpress",
"common",
"compiler",
"compiler-cli",
"core",
docs: rename the "aio" component to "docs-infra" (#24295) The legacy "aio" is still active for currently pending PRs, The GH label has been renamed as well PR Close #24295
2018-06-04 10:00:08 -07:00
"docs-infra",
feat(elements): add support for creating custom elements (#22413) PR Close #22413
2018-02-28 09:45:11 -08:00
"elements",
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 16:24:47 -08:00
"forms",
"http",
docs(ivy): add Ivy as a recognized label (#21428) PR Close #21428
2018-01-09 13:46:19 -08:00
"ivy",
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 16:24:47 -08:00
"language-service",
test: add 'localize' as an allowed commit message scope (#34974) It seems that we missed adding it before and listed all the localize fixes under 'ivy'. PR Close #34974
2020-01-26 13:44:55 -08:00
"localize",
build: add `ngcc` as a valid commit message scope (#32144) PR Close #32144
2019-08-15 00:32:15 +03:00
"ngcc",
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 16:24:47 -08:00
"platform-browser",
"platform-browser-dynamic",
"platform-server",
"platform-webworker",
"platform-webworker-dynamic",
"router",
feat(service-worker): introduce the @angular/service-worker package (#19274) This service worker is a conceptual derivative of the existing @angular/service-worker maintained at github.com/angular/mobile-toolkit, but has been rewritten to support use across a much wider variety of applications. Entrypoints include: @angular/service-worker: a library for use within Angular client apps to communicate with the service worker. @angular/service-worker/gen: a library for generating ngsw.json files from glob-based SW config files. @angular/service-worker/ngsw-worker.js: the bundled service worker script itself. @angular/service-worker/ngsw-cli.js: a CLI tool for generating ngsw.json files from glob-based SW config files.
2017-09-28 16:18:12 -07:00
"service-worker",
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 16:24:47 -08:00
"upgrade",
"packaging",
build: allow "zone.js" as scope for commit messages (#31277) Adds `zone.js` as valid scope for commit messages. This is necessary because the `zone.js` repository has been moved into the mono-repo and future changes should be categorized properly through commit messages. Currently the pre-commit git hook or CircleCI will fail when `zone.js` is used as commit scope. PR Close #31277
2019-06-26 10:39:23 +02:00
"changelog",
"zone.js"
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 16:24:47 -08:00
]
}
Reference in New Issue Copy Permalink