Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report bugs at https://github.com/amjith/fuzzyfinder/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues for bugs. Anything tagged with “bug” is open to whoever wants to implement it.
Look through the GitHub issues for features. Anything tagged with “feature” is open to whoever wants to implement it.
fuzzyfinder could always use more documentation, whether as part of the official fuzzyfinder docs, in docstrings, or even on the web in blog posts, articles, and such.
Ready to contribute? Here’s how to set up fuzzyfinder for local development.
Fork the fuzzyfinder repo on GitHub.
Clone your fork locally:
$ git clone email@example.com:your_name_here/fuzzyfinder.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ mkvirtualenv fuzzyfinder $ cd fuzzyfinder/ $ pip install -r dev-requirements.txt
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, check that your changes pass the tests. This project uses py.test for testing and tox for running the tests on multiple versions of python:
$ py.test $ tox
To get tox, just pip install tox into your virtualenv.
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.