build: add `ngcc` as a valid commit message scope (#32144)

PR Close #32144
This commit is contained in:
George Kalpakas 2019-08-15 00:32:15 +03:00 committed by Andrew Kushnir
parent 2e4d17f3a9
commit 3cf2005a93
3 changed files with 4 additions and 1 deletions

View File

@ -233,6 +233,7 @@ There are currently a few exceptions to the "use package name" rule:
* **docs-infra**: used for docs-app (angular.io) related changes within the /aio directory of the * **docs-infra**: used for docs-app (angular.io) related changes within the /aio directory of the
repo repo
* **ivy**: used for changes to the [Ivy renderer](https://github.com/angular/angular/issues/21706). * **ivy**: used for changes to the [Ivy renderer](https://github.com/angular/angular/issues/21706).
* **ngcc**: used for changes to the [Angular Compatibility Compiler](./packages/compiler-cli/ngcc/README.md)
* none/empty string: useful for `style`, `test` and `refactor` changes that are done across all * none/empty string: useful for `style`, `test` and `refactor` changes that are done across all
packages (e.g. `style: add missing semicolons`) and for docs changes that are not related to a packages (e.g. `style: add missing semicolons`) and for docs changes that are not related to a
specific package (e.g. `docs: fix typo in tutorial`). specific package (e.g. `docs: fix typo in tutorial`).

View File

@ -12,7 +12,6 @@ The owner of the component is then responsible for the secondary / component-lev
The caretaker should be able to determine which component the issue belongs to. The caretaker should be able to determine which component the issue belongs to.
The components have a clear piece of source code associated with it within the `/packages/` folder of this repo. The components have a clear piece of source code associated with it within the `/packages/` folder of this repo.
* `comp: docs-infra` - the angular.io application and docs-related tooling
* `comp: animations` * `comp: animations`
* `comp: bazel` - @angular/bazel rules * `comp: bazel` - @angular/bazel rules
* `comp: benchpress` * `comp: benchpress`
@ -21,6 +20,8 @@ The components have a clear piece of source code associated with it within the `
* `comp: core & compiler` - because core, compiler, compiler-cli and * `comp: core & compiler` - because core, compiler, compiler-cli and
browser-platforms are very intertwined, we will be treating them as one browser-platforms are very intertwined, we will be treating them as one
* `comp: ivy` - a subset of core representing the new Ivy renderer. * `comp: ivy` - a subset of core representing the new Ivy renderer.
* `comp: ngcc` - a subset of ivy representing the [Angular Compatibility Compiler](../packages/compiler-cli/ngcc/README.md)
* `comp: docs-infra` - the angular.io application and docs-related tooling
* `comp: elements` * `comp: elements`
* `comp: forms` * `comp: forms`
* `comp: http` * `comp: http`

View File

@ -27,6 +27,7 @@
"http", "http",
"ivy", "ivy",
"language-service", "language-service",
"ngcc",
"platform-browser", "platform-browser",
"platform-browser-dynamic", "platform-browser-dynamic",
"platform-server", "platform-server",