Thank you for your interest in contributing to the Baseball Strategy Assistant! Contributions are welcome from everyone, whether you're fixing bugs, improving documentation, or proposing new features. Please take a moment to review this guide to ensure a smooth and enjoyable contribution process.
If you find a bug, please open an issue and include:
- A clear description of the problem.
- Steps to reproduce the issue.
- Screenshots or error messages (if applicable).
Have an idea to improve the project? Open an issue and:
- Describe the feature or enhancement.
- Explain why it would be valuable.
- Provide examples or mockups (if possible).
Want to contribute code? Follow these steps:
- Fork the repository and clone it locally.
- Create a new branch for your changes:
git checkout -b feature/your-feature-name
- Make your changes and test them thoroughly.
- Commit your changes with a clear and descriptive message:
git commit -m "Add: New feature to explain pitch types"
- Push your branch to your forked repository:
git push origin feature/your-feature-name
- Open a Pull Request (PR) and describe your changes in detail.
-
Clone the repository:
git clone https://github.com/Eusha425/baseball-strategy-assistant.git cd baseball-strategy-assistant
-
Set up a virtual environment:
python -m venv .venv source .venv/bin/activate # On Windows: .venv\Scripts\activate
-
Install dependencies:
pip install -r requirements.txt
-
Run the app locally:
streamlit run main.py
Before submitting a PR, ensure your changes pass all tests:
- Run the app and verify functionality.
- Check for linting errors:
pylint mlb_client gemini_client main.py
- Format your code:
black .
Your contributions help make this project better for everyone.
By contributing, you agree that your contributions will be licensed under the MIT License.