This document explains how to propose changes to the project.
Minor typos or grammatical errors in the documentation can be corrected directly using the GitHub web interface, provided the changes are made in the appropriate source file.
Before opening a new issue, you must review existing open and closed issues for similar problems or questions. If you can't find a solution, please, feel free to open a new issue containing as much detail as possible including: a clear description of the issue, steps to reproduce the problem, relevant error messages, and environment setups.
Before submitting a substantial pull request (PR), you must first file an issue to ensure the team agrees that the problem needs to be addressed. For bugs, create a corresponding issue and include a minimal reproducible example (reprex) to illustrate the problem.
Create a dedicated Git branch for each PR. Follow the PEP8 style guide (for Python code) when writing new code.
This project is governed by a Contributor Code of Conduct. By contributing, you agree to adhere to its terms.
These guidelines are adapted from the dplyr contributing guidelines.