You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9-4
Original file line number
Diff line number
Diff line change
@@ -227,10 +227,15 @@ The following is the list of supported scopes:
227
227
228
228
There are currently a few exceptions to the "use package name" rule:
229
229
230
-
***packaging**: used forchanges that change the npm package layoutin all of our packages, e.g. public path changes, package.json changes done to all packages, d.ts file/format changes, changes to bundles, etc.
230
+
***packaging**: used forchanges that change the npm package layoutin all of our packages, e.g.
231
+
public path changes, package.json changes done to all packages, d.ts file/format changes, changes
232
+
to bundles, etc.
231
233
***changelog**: used forupdating the release notesin CHANGELOG.md
232
-
***aio**: used for docs-app (angular.io) related changes within the /aio directory of the repo
233
-
* none/empty string: useful for`style`, `test` and `refactor` changes that are done across all packages (e.g. `style: add missing semicolons`)
234
+
***docs-infra**: used for docs-app (angular.io) related changes within the /aio directory of the
235
+
repo
236
+
* none/empty string: useful for`style`, `test` and `refactor` changes that are done across all
237
+
packages (e.g. `style: add missing semicolons`) and for docs changes that are not related to a
238
+
specific package (e.g. `docs: fix typo in tutorial`).
234
239
235
240
### Subject
236
241
The subject contains a succinct description of the change:
@@ -269,7 +274,7 @@ changes to be accepted, the CLA must be signed. It's a quick process, we promise
Note that if you have more than one Git identity, it is important to verify that you are logged in with the same ID with which you signed the CLA, before you commit changes. If not, your PR will fail the CLA check.
277
+
Note that if you have more than one Git identity, it is important to verify that you are logged in with the same ID with which you signed the CLA, before you commit changes. If not, your PR will fail the CLA check.
0 commit comments