build: add commit message scope for migration changes (#36390)

This is a proposal commit that adds a separate scope for
migration changes. The motiviation is that migrations aren't
necessarily always affecting `@angular/core`, but are just
stored in the core package for a canonical location when
someone runs `ng update`. Additionally, it rather seems confusing in the
changelog if migration changes are listed under `core`.

PR Close #36390
This commit is contained in:
Paul Gschwendtner 2020-04-02 11:11:00 +02:00 committed by atscott
parent d76a872efb
commit bd9c1e6cfc
2 changed files with 2 additions and 0 deletions

View File

@ -32,6 +32,7 @@ const commitMessage = {
'http', 'http',
'language-service', 'language-service',
'localize', 'localize',
'migrations',
'ngcc', 'ngcc',
'packaging', 'packaging',
'platform-browser', 'platform-browser',

View File

@ -236,6 +236,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
* **dev-infra**: used for dev-infra related changes within the directories /scripts, /tools and /dev-infra * **dev-infra**: used for dev-infra related changes within the directories /scripts, /tools and /dev-infra
* **migrations**: used for changes to the `ng update` migrations.
* **ngcc**: used for changes to the [Angular Compatibility Compiler](./packages/compiler-cli/ngcc/README.md) * **ngcc**: used for changes to the [Angular Compatibility Compiler](./packages/compiler-cli/ngcc/README.md)
* **ve**: used for changes specific to ViewEngine (legacy compiler/renderer). * **ve**: used for changes specific to ViewEngine (legacy compiler/renderer).
* 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