Contributions are welcome, and they are greatly appreciated! Every little bit
helps, and credit will always be given.
You can report bugs at https://github.com/zfit/zfit/issues.
You can send feedback by filing an issue at https://github.com/zfit/zfit/issues or,
for more informal discussions, you can also join our Gitter channel.
Ready to contribute? Here’s how to set up zfit for local development.
Fork the zfit repo on GitHub.
Clone your fork locally:
$ git clone firstname.lastname@example.org:your_name_here/zfit.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 zfit
$ cd zfit/
$ python setup.py develop
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
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. The test suite is going
to run again, testing all the necessary Python versions.
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. Put
your new functionality into a function with a docstring, and add the
necessary explanations in the corresponding rst file in the docs.
If any math is involved, please document the exact formulae implemented
in the docstring/docs.
The pull request should work for Python 3.6 and 3.7. Check
and make sure that the tests pass for all supported Python versions.