Skip to content

Latest commit

 

History

History
50 lines (29 loc) · 2.17 KB

CONTRIBUTING.md

File metadata and controls

50 lines (29 loc) · 2.17 KB

Contributing to Sepantia

Welcome to the Sepantia-Chess Engine project! We're glad you're interested in contributing. Please take a moment to read through this document to understand how you can contribute to the project.

How to Contribute

There are several ways you can contribute to the Python Chess Engine project:

1. Reporting Issues

If you encounter any bugs, errors, or have suggestions for improvements, please open an issue on our GitHub repository. When reporting issues, please include as much detail as possible, including steps to reproduce the issue and your operating system/environment.

2. Fixing Issues

You can contribute by fixing existing issues or implementing new features. Here's how:

  • Fork the repository to your GitHub account.
  • Create a new branch for your changes: git checkout -b fix-issue-# (where # is the issue number).
  • Make your changes.
  • Test your changes thoroughly.
  • Commit your changes: git commit -am "Fix #"
  • Push your changes to your fork: git push origin fix-issue-#
  • Open a pull request with a clear description of your changes and reference to the related issue.

3. Improving Documentation

You can contribute by improving the project's documentation. This includes fixing typos, adding examples, or clarifying existing documentation.

4. Providing Feedback

You can provide feedback on the project's direction, features, and implementation by participating in discussions on issues or pull requests.

Code Style

When contributing code, please follow these guidelines:

  • Follow PEP 8 for Python code style.
  • Use clear and descriptive variable/function names.
  • Write docstrings for functions and classes to explain their purpose and usage.

License

By contributing to the Python Chess Engine project, you agree that your contributions will be licensed under the project's MIT License.

Contact

If you have any questions or need further assistance, feel free to contact us via email or open an issue on GitHub.

Thank you for your contributions!