22
33This document contains basic guidelines to make contributing to this project as easy and transparent as possible, whether it's:
44
5- - Reporting a bug
6- - Discussing the current state of the code
7- - Submitting a fix
8- - Proposing new features
9- - Becoming a maintainer
5+ - Reporting a bug
6+ - Discussing the current state of the code
7+ - Submitting a fix
8+ - Proposing new features
9+ - Becoming a maintainer
1010
1111## Pull requests are actively welcomed
1212
13131 . Fork the repo and create your branch from ` master ` .
14142 . If you've added code that should be tested, add tests.
15153 . If you've changed APIs, update the documentation.
16- 5 . Make sure your code lints.
17- 6 . Issue your pull request.
16+ 4 . Make sure your code lints.
17+ 5 . Issue your pull request.
1818
1919## Any contributions you make will be under the MIT Software License
2020
@@ -28,13 +28,13 @@ All bugs are tracked using GitHub issues to track public bugs. Report a bug by [
2828
2929** Great bug reports** tend to have:
3030
31- - A quick summary and/or background
32- - Steps to reproduce
33- - Be specific!
34- - Give sample code if you can.
35- - What you expected would happen
36- - What actually happens
37- - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
31+ - A quick summary and/or background
32+ - Steps to reproduce
33+ - Be specific!
34+ - Give sample code if you can.
35+ - What you expected would happen
36+ - What actually happens
37+ - Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
3838
3939## License
4040
0 commit comments