# .. highlight:: shell
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 by opening a new issue.
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” and “help wanted” is open to whoever wants to implement it.
Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.
hankel could always use more documentation, whether as part of the official hankel docs, in docstrings, or even on the web in blog posts, articles, and such.
In particular, if you have used hankel in a novel way, please consider submitting a script or Jupyter notebook as “demo” documentation.
Ready to contribute? Here’s how to set up hankel for local development.
Fork the hankel repo on GitHub.
Clone your fork locally:
$ git clone firstname.lastname@example.org:your_name_here/hankel.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 hankel $ cd hankel/ $ pip install -e .[dev]
Note the optional extra install of the development dependencies.
If you are using conda, setup your environment the usual way, i.e.
conda create -n hankelbefore installing as above.
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 flake8 and the tests, including testing other Python versions with tox:
$ flake8 hankel tests $ py.test $ tox
To get flake8 and tox, just pip install them 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.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
The pull request should include tests.
If the pull request adds functionality, the docs should be updated. Ensure your new functionality is documented in the relevant docstring (we use Numpy-style docstrings). If it is a significant feature, it will also be preferable to add a demo notebook to the
If you implement an important new feature, consider adding the feature to the list in README.rst.
The pull request should work for Python 2.7, 3.5, 3.6, and 3.7. Check https://travis-ci.org/steven-murray/hankel/pull_requests and make sure that the tests pass for all supported Python versions.
To run a subset of tests:
$ py.test tests.test_hankel
A reminder for the maintainers on how to deploy. Make sure all your changes are committed (including an entry in HISTORY.rst). Then run:
$ bumpversion patch # possible: major / minor / patch $ git push $ git push --tags
Travis will then deploy to PyPI if tests pass.