We appreciate all contributions to this project, whether they are simple questions or full-fledged pull requests.
Your contribution may fall into one of the following categories:
- You have a question or an idea.
- You believe you may have found a bug, including unexpected behavior.
- You want to make changes to the codebase, such as fixing a bug, adding a new feature, or updating documentation.
Below are the steps to take for each category:
- Check the Discussions section to see if someone else has already posted a similar question or idea.
- If your search did not yield any relevant results, start a new discussion within the relevant category.
- Check the Issues section to see if someone else has already raised the same issue.
- If your search did not yield any relevant results, create a new issue.
- Ensure you provide enough information to help the community understand the cause and context of the problem. Depending on the issue, you may want to include:
- The version number of the release causing the problem.
- Detailed information about the use case and unexpected behavior.
- Information about the operating system.
- Apply relevant labels to the newly created issue.
- Make sure you are familiar with forking a repository and creating a pull request on GitHub.
- Prepare your local machine by installing Hatch.
- After forking the project, run the command
hatch env create
to create the virtual environment. - Before committing changes, run the command
hatch run checks
to ensure all checks pass, including formatting, linting, typing, and tests with coverage. - Once you have pushed changes to your fork, you can create a pull request.
If you believe that you have made a significant contribution to this project but do not know how to write tests, run them, or generate documentation, do not let this discourage you from submitting a pull request. We are here to help you out! Simply submit the pull request, but keep in mind that you might be requested to add more commits to your pull request.