# Contributing Thank you for your interest in contributing! We welcome contributions of all kinds, including new features, bug fixes, and documentation improvements. Please take a moment to review this document to make the contribution process easy and effective for everyone involved. If you have any questions, feel free to reach out by opening an issue or contacting the maintainers directly. ## Table of Contents 1. [How to Report an Issue](#how-to-report-an-issue) 2. [Submitting a Pull Request](#submitting-a-pull-request) 3. [Coding Guidelines](#coding-guidelines) 4. [Code of Conduct](#code-of-conduct) ## How to Report an Issue If you encounter any bugs or have feature requests, please create an issue on our GitHub repository. 1. Go to the [Issues]((githubrepo)/issues) page. 2. Click on "New Issue". 3. Select the "Bug report" or "Feature request". 4. Fill in the details as prompted by the template. If your issue does not fit the provided templates, feel free to create an issue without following them. Provide as much detail as possible to help us understand and address your concern. ## Submitting a Pull Request To submit a pull request, please follow these steps: 1. **Fork the Repository**: - Navigate to the [repository]((githubrepo)). - Click the "Fork" button in the top-right corner. 2. **Clone the Forked Repository**: ```sh git clone (githubrepo) cd sports-manager ``` 3. **Create a Branch**: ```sh git checkout -b ``` 4. **Make Your Changes**: - Implement your feature, bug fix, or documentation improvement. - If you're making changes to the code, write some tests. - Ensure your code follows our [Coding Guidelines](#coding-guidelines). 5. **Commit Your Changes**: ```sh git add . git commit -m "Description of your changes" ``` 6. **Push to Your Fork**: ```sh git push origin your-branch-name ``` 7. **Create a Pull Request**: - Go to your fork on GitHub. - Click on the "Compare & pull request" button. - Fill in the details of your pull request and submit. We will review your pull request and provide feedback. Please be responsive to our comments and make the necessary adjustments. ## Coding Guidelines To ensure consistency and maintainability of the codebase, please adhere to the following guidelines: - Follow the Ruby community's [style guide](https://rubystyle.guide/). - Write tests for your changes. - Ensure all tests pass before submitting a pull request. - Document public methods and classes. ## Code of Conduct By participating in this project, you agree to abide by our [Code of Conduct](./CODE_OF_CONDUCT.md). Please be respectful and considerate in all interactions.