Skip to content

Commit 5d327d7

Browse files
committed
TT-104 fix: Semantic bot is not working when merging changes to UI
1 parent 3b4f11a commit 5d327d7

File tree

2 files changed

+11
-8
lines changed

2 files changed

+11
-8
lines changed

README.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ Run `npm install` to install the required node_modules for this project.
3131
Run `ng serve` to run the app in dev mode. After executing this command, you can navigate to `http://localhost:4200/` to see the app working.
3232
The app will automatically reload if you change anything in the source files.
3333

34-
## Prepare your environment
34+
## Prepare your environment
3535

3636
### Set environment variables
37-
Create a file keys.ts with the content pinned in our slack channel:
37+
Create a file keys.ts in the path `src/enviroment` with the content pinned in our slack channel:
3838

3939
```
4040
export const AUTHORITY = 'XXX';
@@ -54,9 +54,9 @@ Install the following extensions:
5454
- Go to user settings (`settings.json`) and enable formatting on save: `"editor.formatOnSave": true`.
5555

5656
### Commit messages format
57-
Commit messages' format follows the [Conventional Commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification,
58-
and specifically we are relying on the [Angular commit specifications](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) to bump the [semantic version](https://semver.org/) and generate app change log.
59-
57+
Commit messages' format follows the [Conventional Commits guidelines](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification,
58+
and specifically we are relying on the [Angular commit specifications](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) to bump the [semantic version](https://semver.org/) and generate app change log.
59+
6060
Below there are some common examples you can use for your commit messages:
6161

6262
- **feat**: A new feature.
@@ -67,10 +67,13 @@ Install the following extensions:
6767
- **docs**: Documentation only changes.
6868
- **refactor**: A code change that neither fixes a bug nor adds a feature.
6969
- **style**: Changes that do not affect the meaning of the code (typos, white-space, formatting, missing semi-colons, etc).
70-
It is important to mention that this key is not related to css styles.
70+
It is important to mention that this key is not related to css styles.
7171
- **test**: Adding missing tests or correcting existing tests.
7272
### Example
73-
fix: #48 implement semantic versioning.
73+
TT-48 fix: #48 implement semantic versioning.
74+
75+
Prefix to use in the space fix:
76+
`(fix: |feat: |perf: |build: |ci: |docs: |refactor: |style: |test: )`
7477

7578
## Code scaffolding
7679
Run `ng generate component component-name` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module`.

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@
9999
},
100100
"config": {
101101
"commit-message-validator": {
102-
"pattern": "^(TT-)[0-9].*(fix: |feat: |perf: |build: |ci: |docs: |refactor: |style: |test: )",
102+
"pattern": "^((TT-)[0-9].*(fix: |feat: |perf: |build: |ci: |docs: |refactor: |style: |test: ))",
103103
"errorMessage": "Your commit message needs to start with TT-number fix:, feat:, or perf: followed by any commit message, e.g. TT-43 fix: any commit message"
104104
}
105105
},

0 commit comments

Comments
 (0)