Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
By contributing, you agree that we may redistribute your work under our license. In exchange, we will address your issues and/or assess your change proposal as promptly as we can, and help you become a member of our community. Everyone involved agrees to abide by our code of conduct.
You can contribute in many ways:
Report bugs at https://github.com/chuangw46/eda_utils_py/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" 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.
eda_utils_py could always use more documentation, whether as part of the official eda_utils_py 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/chuangw46/eda_utils_py/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 :)
Ready to contribute? Here's how to set up eda_utils_py for local development.
Fork the eda_utils_py repo on GitHub.
Clone your fork locally:
$ git clone git@github.com:your_name_here/eda_utils_py.git
Install your local copy (it is recommended to do this with a virtual environment). The method of installation will depend on the packaging library being used. For example, if setuptools is being used (a setup.py file is present), install eda_utils_py with:
$ python setup.py installIf poetry is being used (poetry.lock and pyproject.toml files are present), install eda_utils_py with:
$ poetry installCreate a branch for local development and make your changes locally:
$ git checkout -b name-of-your-bugfix-or-feature
When you're done making changes, check that your changes conform to any code formatting requirements and pass any tests. For example, if the package uses the poetry package management library, black formatting style and pytest for testing:
$ poetry run black eda_utils_py $ poetry run pytest
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:
- The pull request should include additional tests if appropriate.
- If the pull request adds functionality, the docs should be updated.
- The pull request should work for all currently supported operating systems and versions of Python.
Please note that the eda_utils_py project is released with a Contributor Code of Conduct. By contributing to this project you agree to abide by its terms.