From bd9c1e6cfcfc4fb7da242134b80424e67cca2c65 Mon Sep 17 00:00:00 2001 From: Paul Gschwendtner Date: Thu, 2 Apr 2020 11:11:00 +0200 Subject: [PATCH] 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 --- .ng-dev/config.ts | 1 + CONTRIBUTING.md | 1 + 2 files changed, 2 insertions(+) diff --git a/.ng-dev/config.ts b/.ng-dev/config.ts index ab65c9131e..eb29a1bc6f 100644 --- a/.ng-dev/config.ts +++ b/.ng-dev/config.ts @@ -32,6 +32,7 @@ const commitMessage = { 'http', 'language-service', 'localize', + 'migrations', 'ngcc', 'packaging', 'platform-browser', diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9d49e0bdb5..4eb4782b9a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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 repo * **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) * **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