Thank you for your interest in contributing to FixThisChris! You don't need to be a programmer to contribute. Whether you're looking to report a bug, propose a new feature, or contribute code, improve docs, this guide will help you get started. Together, we can make FixThisChris a valuable tool for the GitHub community.
- Code of Conduct
- Getting Started
- Reporting Bugs
- Suggesting Enhancements
- Code Contributions
- Style Guidelines
- Community
By participating in this project, you are expected to uphold our Code of Conduct.
- Make sure you have a GitHub account.
- Fork the repository on GitHub.
- Clone your fork locally.
- Install the required dependencies by following the instructions in the README.md.
- Check the issue tracker to see if your issue has already been reported.
- If your issue hasn't been reported, open a new issue.
- Be sure to include a title and clear description, and as much relevant information as possible.
- Fork the repository and create a new branch from
main
for your work. - Make sure your code passes any lint checks.
- Include relevant test cases for your update.
- Submit a pull request targeting the
main
branch of the repository. - Provide a clear description of your changes.
This project adheres to the PEP 8 coding style. Please take a moment to review the guidelines.
Join our Community Discord to discuss the development of FixThisChris, ask questions, and connect with other contributors.