Thank you for your interest in contributing to Whistleblower! We welcome contributions from the community and are grateful for any help you can provide.
- Code of Conduct
- Getting Started
- How to Contribute
- Development Setup
- Pull Request Process
- Coding Guidelines
- Questions
- Recognition
By participating in this project, you agree to maintain a respectful and inclusive environment for all contributors. Please be kind and considerate in all interactions.
- Fork the repository on GitHub
- Clone your fork locally:
git clone https://github.com/your-username/whistleblower.git cd whistleblower - Add the upstream repository:
git remote add upstream https://github.com/Repello-AI/whistleblower.git
There are many ways to contribute to Whistleblower:
- Report bugs - Help us identify and fix issues
- Suggest features - Share ideas for new functionality
- Improve documentation - Help make our docs clearer and more comprehensive
- Submit bug fixes - Fix issues you've found
- Add new features - Implement requested features or your own ideas
- Write tests - Improve test coverage
- Improve UI/UX - Enhance the Gradio interface
-
Install Python (version 3.8 or higher recommended)
-
Create a virtual environment:
python -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate
-
Install dependencies:
pip install -r requirements.txt
-
Set up your environment variables:
- Create a
.envfile for your OpenAI API key (never commit this file)
- Create a
-
Verify the installation:
python main.py --help
-
Create a new branch for your changes:
git checkout -b feature/your-feature-name
Use descriptive branch names:
feature/add-new-model-supportfix/gradio-input-validationdocumentation/update-readme
-
Make your changes following our coding guidelines
-
Test your changes thoroughly
-
Commit your changes with clear, descriptive messages:
git commit -m "Add support for Claude API integration" -
Push to your fork:
git push origin feature/your-feature-name
-
Open a Pull Request on GitHub:
- Provide a clear title and description
- Reference any related issues (e.g., "Fixes #123")
- Include screenshots for UI changes
- List any breaking changes
-
Respond to feedback - Be open to suggestions and iterate on your PR
- Follow PEP 8 style guidelines
- Use meaningful variable and function names
- Keep functions focused and modular
- Add docstrings to functions and classes
Have questions about contributing? Here's how to get help:
- GitHub Issues - Open an issue with the
questionlabel - Documentation - Check the README first
- Repello AI - Visit repello.ai for more information
Contributors will be recognized in our repository and documentation. Thank you for helping make Whistleblower better!
Note: By contributing to this project, you agree that your contributions will be licensed under the same license as the project.