|
| 1 | +# Contributing |
| 2 | + |
| 3 | +If you want to participate in this project, please follow this guidline. |
| 4 | + |
| 5 | +Fork and clone this repository: |
| 6 | + |
| 7 | +```bash |
| 8 | +git clone git@github.com:your-username/sruthi.git |
| 9 | +``` |
| 10 | + |
| 11 | +Install the dependencies using `pip`: |
| 12 | + |
| 13 | +```bash |
| 14 | +pip install -r requirements.txt |
| 15 | +pip install -r test-requirements.txt |
| 16 | +``` |
| 17 | + |
| 18 | +Make sure the tests pass: |
| 19 | + |
| 20 | +```bash |
| 21 | +pytest |
| 22 | +``` |
| 23 | + |
| 24 | +To ensure a good quality of the code use `flake8` to check the code style: |
| 25 | + |
| 26 | +```bash |
| 27 | +flake8 --install-hook git |
| 28 | +``` |
| 29 | + |
| 30 | +## Create a pull request |
| 31 | + |
| 32 | +1. Choose the `develop` branch as a target for new/changed functionality, `master` should only be targeted for urgent bugfixes. |
| 33 | +2. While it's not strictly required, it's highly recommended to create a new branch on your fork for each pull request. |
| 34 | +3. Push to your fork and [submit a pull request][pr]. |
| 35 | +4. Check if the [build ran successfully][ci] and try to improve your code if not. |
| 36 | + |
| 37 | +At this point you're waiting for my review. |
| 38 | +I might suggest some changes or improvements or alternatives. |
| 39 | + |
| 40 | +Some things that will increase the chance that your pull request is accepted: |
| 41 | + |
| 42 | +* Write tests. |
| 43 | +* Follow the Python style guide ([PEP-8][pep8]). |
| 44 | +* Write a [good commit message][commit]. |
| 45 | + |
| 46 | +[pr]: https://github.com/metaodi/sruthi/compare/ |
| 47 | +[ci]: https://github.com/metaodi/sruthi/actions |
| 48 | +[pep8]: https://www.python.org/dev/peps/pep-0008/ |
| 49 | +[commit]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html |
0 commit comments