@@ -14,14 +14,14 @@ helpful.
14
14
15
15
Before you submit your pull request (PR) consider the following guidelines:
16
16
17
- - Fork Design-tokens into your namespace by using the fork button on github.
18
- - Make your changes in a new git branch: ` git checkout -b my-fix-branch master `
19
- - Create your bugfix/feature including appropriate tests.
20
- - Test your changes with our supported browsers.
21
- - Run unit tests and ensure that all tests pass.
22
- - Push your branch to GitHub.
23
- - Create a new pull request from your branch against the angular-components: master
24
- branch.
17
+ - Fork Design-tokens into your namespace by using the fork button on github.
18
+ - Make your changes in a new git branch: ` git checkout -b my-fix-branch master `
19
+ - Create your bugfix/feature including appropriate tests.
20
+ - Test your changes with our supported browsers.
21
+ - Run unit tests and ensure that all tests pass.
22
+ - Push your branch to GitHub.
23
+ - Create a new pull request from your branch against the angular-components: master
24
+ branch.
25
25
26
26
## Commit message guidelines
27
27
@@ -34,10 +34,11 @@ Before you submit your pull request (PR) consider the following guidelines:
34
34
│ elements|forms|http|language-service|localize|platform-browser|
35
35
│ platform-browser-dynamic|platform-server|router|service-worker|
36
36
│ upgrade|zone.js|packaging|changelog|dev-infra|docs-infra|migrations|
37
- │
37
+ │
38
38
│
39
39
└─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
40
40
```
41
+
41
42
Each commit message consists of a ` type ` , ` scope ` and ` subject ` (message).
42
43
The ` type ` and ` subject ` are mandatory, the ` scope ` is optional in some specific
43
44
cases. Format: ` <type>(<scope>): <subject> `
@@ -46,17 +47,17 @@ cases. Format: `<type>(<scope>): <subject>`
46
47
47
48
Must be one of the following:
48
49
49
- - ** feat** : A new feature
50
- - ** fix** : A bug fix
51
- - ** docs** : Documentation only changes
52
- - ** style** : Changes that do not affect the meaning of the code (white-space,
53
- formatting, missing semi-colons, etc)
54
- - ** refactor** : A code change that neither fixes a bug nor adds a feature
55
- - ** test** : Adding missing tests or correcting existing tests
56
- - ** ci** : Changes that affect the CI
57
- - ** build** : Changes that affect the build system like npm scripts or
58
- angular-cli related changes
59
- - ** chore** : Other changes that don't modify src or test files
50
+ - ** feat** : A new feature
51
+ - ** fix** : A bug fix
52
+ - ** docs** : Documentation only changes
53
+ - ** style** : Changes that do not affect the meaning of the code (white-space,
54
+ formatting, missing semi-colons, etc)
55
+ - ** refactor** : A code change that neither fixes a bug nor adds a feature
56
+ - ** test** : Adding missing tests or correcting existing tests
57
+ - ** ci** : Changes that affect the CI
58
+ - ** build** : Changes that affect the build system like npm scripts or
59
+ angular-cli related changes
60
+ - ** chore** : Other changes that don't modify src or test files
60
61
61
62
### Scope
62
63
@@ -100,7 +101,7 @@ BREAKING CHANGE: The method has been removed.
100
101
Describe reasons.
101
102
```
102
103
103
- ## Code reviews and PRs
104
+ ## Code reviews and PRs
104
105
105
106
### Open PR
106
107
0 commit comments