Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Report bugs at https://github.com/testsuite/mockingbird/issues.
If you are reporting a bug, please include:
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.
Mockingbird could always use more documentation, whether as part of the official Mockingbird docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue at https://github.com/testsuite/mockingbird/issues.
If you are proposing a feature:
Ready to contribute? Here’s how to set up mockingbird for local development.
Fork the mockingbird repo on GitHub.
Clone your fork locally:
$ git clone git@github.com:your_name_here/mockingbird.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ cd mockingbird
$ mkvirtualenv mockingbird -r requirements/development.txt -a ${pwd}
$ cdproject
$ 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.
5. When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:
$ tox
Run pyformat to ensure that your changes conform to the coding style guidelines of this project:
$ pyformat . -i -r
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.
Before you submit a pull request, check that it meets these guidelines: