Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
Check the projects on GitHub, you might help coding a planned feature.
Bug reports or feature requests¶
nitpick could always use more documentation, whether as part of the official docs, in docstrings, or even on the web in blog posts, articles, and such.
To set up Nitpick for local development:
Fork Nitpick (look for the “Fork” button).
Clone your fork locally:
cd ~/Code git clone email@example.com:your_name_here/nitpick.git cd nitpick
Install Poetry globally using the recommended way.
Create your virtualenv with pyenv (or some other tool you prefer):
pyenv virtualenv 3.5.6 nitpick pyenv activate nitpick
poetry install # Output: # Installing dependencies from lock file # ...
Create a branch for local development:
git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
When you’re done making changes, run pre-commit checks and tests with:
Commit your changes and push your branch to GitHub:
git add . git commit -m "Your detailed description of your changes." git push origin name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
If your pull request is accepted, all your commits will be squashed into one, and the Conventional Commits Format will be used on the commit message.
Pull Request Guidelines¶
If you need some code review or feedback while you’re developing the code just make the pull request.
For merging, you should:
Include passing tests (run
make test) 1.
Update documentation when there’s new API, functionality etc.
Add yourself to