Skip to content

Commit 188c5b9

Browse files
authored
Update CONTRIBUTING.md
1 parent 5a9e7d3 commit 188c5b9

File tree

1 file changed

+6
-11
lines changed

1 file changed

+6
-11
lines changed

docs/CONTRIBUTING.md

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,7 @@ Unsure where to begin contributing to Phonebook? You can start by looking for th
1616
If you have questions about the issue or do not know where to start you can just ask under the issue.
1717

1818
### Open Pull Requests
19-
If you want to open a pull request please use our [template](will be added soon).
20-
21-
### Reviewing a pull request
19+
If you want to open a pull request please use our [template](will be added soon). Please also note the issue which get resolved and stuff the reviewers need to know before reviewing your code.
2220

2321
## What should I know before I get started?
2422
Before you start contributing be sure that you have already taken a look at our [Documentation](https://t-systems-mms.github.io/phonebook/). There you can find all things you need to know before work with the project.
@@ -31,14 +29,11 @@ To provide good code quality we are using prettier to format all files the same
3129
Because of we are using [semantic release](https://github.com/semantic-release/semantic-release) it is important that the git messages, especially the merge messages, follow the [Angular commit Message Convention](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines).
3230
The messages should have the following format: `type(scope): subject`
3331

34-
> *type* -> feat, fix, chore and docs\
35-
> *scope* -> The part of the program which will be affected \
36-
> *subject* -> Description of what has been changed\
32+
- *type* -> feat, fix, chore and docs\
33+
- *scope* -> The part of the program which will be affected \
34+
- *subject* -> Description of what has been changed\
3735

3836
## Additional Notes
3937
### Issue and Pull request labels
40-
tbd..
41-
42-
### Explanation of label "prio"
43-
We have 5 different labels to show the importance of an issue.
44-
tbd..
38+
qualified: You can find additional information of what you need to do to solve this issue.
39+
good-first-issue: This Label represents problems with a lower complexity and a good way to start into the project.

0 commit comments

Comments
 (0)