Thank you for considering contributing to the Chess Master Ultimate project! We welcome contributions from the community to help improve this open-source chess application. This guide outlines how you can contribute effectively.
Please review our Code of Conduct to understand the expectations for all contributors and maintain a welcoming environment.
- Check the Issues page to ensure the bug hasn't already been reported.
- Open a new issue with a clear title and description, including steps to reproduce, expected behavior, and actual behavior.
- Use the bug report template if available.
- Check the Issues page to see if the feature has been proposed.
- Open a new issue with a clear title and detailed description of the feature, including its purpose and potential implementation.
- Use the feature request template if available.
- Fork the Repository:
- Fork the repository at https://github.com/VoxDroid/Chess-Master-Ultimate.
- Clone Your Fork:
git clone https://github.com/<your-username>/Chess-Master-Ultimate
- Create a Feature Branch:
git checkout -b feature/your-feature-name
- Make Changes:
- Follow the coding style and conventions used in the project (e.g., TypeScript, Tailwind CSS, Next.js best practices).
- Ensure your changes are well-documented and include tests if applicable.
- Commit Changes:
- Use clear, descriptive commit messages.
git commit -m "Add your descriptive message here" - Push to Your Fork:
git push origin feature/your-feature-name
- Open a Pull Request:
- Go to the original repository and create a pull request from your branch.
- Use the Pull Request Template to provide details about your changes.
- Reference any related issues (e.g.,
Fixes #123).
- Follow the Getting Started section in the README.md to set up the project locally.
- Ensure you have Node.js (v18.0 or higher) and a package manager (
npmoryarn) installed. - Run
npm installoryarn installto install dependencies. - Start the development server with
npm run devoryarn dev.
- Code Quality: Ensure your code is clean, readable, and follows the project's structure.
- Testing: Add or update tests for new features or bug fixes if applicable.
- Documentation: Update the
README.mdor other documentation if your changes affect usage or setup. - Security: If you identify a security vulnerability, please follow our Security Policy.
- Pull requests will be reviewed by maintainers as soon as possible.
- Expect feedback or requests for changes to ensure quality and consistency.
- Once approved, your changes will be merged into the main branch.
If you have questions or need help, feel free to:
- Open an issue on the Issues page.
- Contact the maintainer at @VoxDroid.
Thank you for contributing to Chess Master Ultimate!