mirror of
https://git.mirrors.martin98.com/https://github.com/bytedance/deer-flow
synced 2025-08-20 12:39:15 +08:00
134 lines
3.0 KiB
Plaintext
134 lines
3.0 KiB
Plaintext
# Contributing to DeerFlow
|
|
|
|
Thank you for your interest in contributing to DeerFlow! We welcome contributions of all kinds from the community.
|
|
|
|
## Ways to Contribute
|
|
|
|
There are many ways you can contribute to DeerFlow:
|
|
|
|
- **Code Contributions**: Add new features, fix bugs, or improve performance
|
|
- **Documentation**: Improve README, add code comments, or create examples
|
|
- **Bug Reports**: Submit detailed bug reports through issues
|
|
- **Feature Requests**: Suggest new features or improvements
|
|
- **Code Reviews**: Review pull requests from other contributors
|
|
- **Community Support**: Help others in discussions and issues
|
|
|
|
## Development Setup
|
|
|
|
1. Fork the repository
|
|
2. Clone your fork:
|
|
```bash
|
|
git clone https://github.com/bytedance/deer-flow.git
|
|
cd deer-flow
|
|
```
|
|
3. Set up your development environment:
|
|
```bash
|
|
# Install dependencies, uv will take care of the python interpreter and venv creation
|
|
uv sync
|
|
|
|
# For development, install additional dependencies
|
|
uv pip install -e ".[dev]"
|
|
uv pip install -e ".[test]"
|
|
```
|
|
4. Configure pre-commit hooks:
|
|
```bash
|
|
chmod +x pre-commit
|
|
ln -s ../../pre-commit .git/hooks/pre-commit
|
|
```
|
|
|
|
## Development Process
|
|
|
|
1. Create a new branch:
|
|
```bash
|
|
git checkout -b feature/amazing-feature
|
|
```
|
|
|
|
2. Make your changes following our coding standards:
|
|
- Write clear, documented code
|
|
- Follow PEP 8 style guidelines
|
|
- Add tests for new features
|
|
- Update documentation as needed
|
|
|
|
3. Run tests and checks:
|
|
```bash
|
|
make test # Run tests
|
|
make lint # Run linting
|
|
make format # Format code
|
|
make coverage # Check test coverage
|
|
```
|
|
|
|
4. Commit your changes:
|
|
```bash
|
|
git commit -m 'Add some amazing feature'
|
|
```
|
|
|
|
5. Push to your fork:
|
|
```bash
|
|
git push origin feature/amazing-feature
|
|
```
|
|
|
|
6. Open a Pull Request
|
|
|
|
## Pull Request Guidelines
|
|
|
|
- Fill in the pull request template completely
|
|
- Include tests for new features
|
|
- Update documentation as needed
|
|
- Ensure all tests pass and there are no linting errors
|
|
- Keep pull requests focused on a single feature or fix
|
|
- Reference any related issues
|
|
|
|
## Code Style
|
|
|
|
- Follow PEP 8 guidelines
|
|
- Use type hints where possible
|
|
- Write descriptive docstrings
|
|
- Keep functions and methods focused and single-purpose
|
|
- Comment complex logic
|
|
- Python version requirement: >= 3.12
|
|
|
|
## Testing
|
|
|
|
Run the test suite:
|
|
```bash
|
|
# Run all tests
|
|
make test
|
|
|
|
# Run specific test file
|
|
pytest tests/integration/test_workflow.py
|
|
|
|
# Run with coverage
|
|
make coverage
|
|
```
|
|
|
|
## Code Quality
|
|
|
|
```bash
|
|
# Run linting
|
|
make lint
|
|
|
|
# Format code
|
|
make format
|
|
```
|
|
|
|
## Community Guidelines
|
|
|
|
- Be respectful and inclusive
|
|
- Follow our code of conduct
|
|
- Help others learn and grow
|
|
- Give constructive feedback
|
|
- Stay focused on improving the project
|
|
|
|
## Need Help?
|
|
|
|
If you need help with anything:
|
|
- Check existing issues and discussions
|
|
- Join our community channels
|
|
- Ask questions in discussions
|
|
|
|
## License
|
|
|
|
By contributing to DeerFlow, you agree that your contributions will be licensed under the MIT License.
|
|
|
|
We appreciate your contributions to making DeerFlow better!
|