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
Report bugs at https://github.com/pandas-dev/pandas-dev-flaker/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.
Fix Bugs
~~~~~~~~
Look through the GitHub issues for bugs. Anything tagged with "bug" and "help
wanted" is open to whoever wants to implement it.
Implement Features
Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it.
Write Documentation
pandas-dev-flaker could always use more documentation, whether as part of the
official pandas-dev-flaker docs, in docstrings, or even on the web in blog posts,
articles, and such.
Submit Feedback
~~~~~~~~~~~~~~~
The best way to send feedback is to file an issue at https://github.com/pandas-dev/pandas-dev-flaker/issues.
If you are proposing a feature:
* Explain in detail how it would work.
* Keep the scope as narrow as possible, to make it easier to implement.
* Remember that this is a volunteer-driven project, and that contributions
are welcome :)
Get Started!
------------
Ready to contribute? Here's how to set up ```` for local development.
1. Fork the ``pandas-dev-flaker`` repo on GitHub at https://github.com/pandas-dev/pandas-dev-flaker.
2. Clone your fork locally::
$ git clone [email protected]:your_name_here/pandas-dev-flaker.git pandas-dev-flaker-dev
$ cd pandas-dev-flaker-dev
3. Set the original repository as upstream::
$ git remote add upstream [email protected]:pandas-dev/pandas-dev-flaker.git
4. Create a Python [virtual environment](https://realpython.com/python-virtual-environments-a-primer/),
and inside it, run:
$ pip install tox pre-commit
$ pre-commit install
5. Create a branch for local development::
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
6. When you're done making changes, check that your changes pass tests:
$ tox -e py
7. 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
8. Submit a pull request through the GitHub website.
Pull Request Guidelines
-----------------------
Before you submit a pull request, check that it meets these guidelines:
1. The pull request should include tests.
2. If the pull request adds functionality, the docs should be updated. Put
your new functionality into a function with a docstring, and add the
feature to the list in README.md.
3. The pull request should work for Python 3.6, 3.7, 3.8, and 3.9.