@@ -8,13 +8,13 @@ If you're a first-time contributor, you can check the issues with [good first is
8
8
9
9
## Before making a pull request
10
10
11
- 1 . Fork [ the repository] ( https://github.com/commitizen-tools/commitizen )
12
- 2 . Clone the repository from you GitHub
13
- 3 . Setup development environment through [ poetry] ( https://python-poetry.org/ ) (` poetry install ` )
14
- 4 . Check out a new branch and add your modification
15
- 5 . Add test cases for all your changes
11
+ 1 . Fork [ the repository] ( https://github.com/commitizen-tools/commitizen ) .
12
+ 2 . Clone the repository from your GitHub.
13
+ 3 . Setup development environment through [ poetry] ( https://python-poetry.org/ ) (` poetry install ` ).
14
+ 4 . Check out a new branch and add your modification.
15
+ 5 . Add test cases for all your changes.
16
16
(We use [ CodeCov] ( https://codecov.io/ ) to ensure our test coverage does not drop.)
17
- 6 . Use [ commitizen] ( https://github.com/commitizen-tools/commitizen ) to do git commit
18
- 7 . Run ` ./scripts/lint ` and ` ./scripts/test ` to ensure you follow the coding style and the tests pass
19
- 8 . Update ` READMD.md ` and ` CHANGELOG.md ` for your changes
17
+ 6 . Use [ commitizen] ( https://github.com/commitizen-tools/commitizen ) to do git commit.
18
+ 7 . Run ` ./scripts/lint ` and ` ./scripts/test ` to ensure you follow the coding style and the tests pass.
19
+ 8 . Update ` READMD.md ` and ` CHANGELOG.md ` for your changes.
20
20
9 . Send a [ pull request] ( https://github.com/commitizen-tools/commitizen/pulls ) 🙏
0 commit comments