|
| 1 | +# Contributing to ACE Framework |
| 2 | + |
| 3 | +Thank you for your interest in contributing to the Agentic Context Engine! We welcome contributions from the community. |
| 4 | + |
| 5 | +## How to Contribute |
| 6 | + |
| 7 | +### Reporting Bugs |
| 8 | + |
| 9 | +Before creating bug reports, please check existing issues to avoid duplicates. When creating a bug report, include: |
| 10 | + |
| 11 | +- A clear and descriptive title |
| 12 | +- Steps to reproduce the issue |
| 13 | +- Expected behavior vs actual behavior |
| 14 | +- Environment details (OS, Python version, package versions) |
| 15 | +- Any relevant error messages or logs |
| 16 | + |
| 17 | +### Suggesting Enhancements |
| 18 | + |
| 19 | +Enhancement suggestions are welcome! Please provide: |
| 20 | + |
| 21 | +- A clear description of the enhancement |
| 22 | +- Use cases and benefits |
| 23 | +- Possible implementation approach (optional) |
| 24 | +- Any potential drawbacks or considerations |
| 25 | + |
| 26 | +### Pull Requests |
| 27 | + |
| 28 | +1. Fork the repository |
| 29 | +2. Create a feature branch (`git checkout -b feature/amazing-feature`) |
| 30 | +3. Make your changes |
| 31 | +4. Run tests to ensure nothing breaks |
| 32 | +5. Commit your changes using conventional commits (see below) |
| 33 | +6. Push to your branch |
| 34 | +7. Open a Pull Request |
| 35 | + |
| 36 | +## Development Setup |
| 37 | + |
| 38 | +```bash |
| 39 | +# Clone your fork |
| 40 | +git clone https://github.com/your-username/agentic-context-engine.git |
| 41 | +cd agentic-context-engine |
| 42 | + |
| 43 | +# Install in development mode with all dependencies |
| 44 | +pip install -e .[all,dev] |
| 45 | + |
| 46 | +# Run tests |
| 47 | +python -m pytest tests/ |
| 48 | + |
| 49 | +# Run linting |
| 50 | +black ace/ |
| 51 | +mypy ace/ |
| 52 | +``` |
| 53 | + |
| 54 | +## Commit Message Format |
| 55 | + |
| 56 | +We use [Conventional Commits](https://www.conventionalcommits.org/) for clear commit history and automatic changelog generation. |
| 57 | + |
| 58 | +Format: `<type>(<scope>): <subject>` |
| 59 | + |
| 60 | +Types: |
| 61 | +- `feat`: New feature |
| 62 | +- `fix`: Bug fix |
| 63 | +- `docs`: Documentation only |
| 64 | +- `style`: Code style changes (formatting, etc.) |
| 65 | +- `refactor`: Code refactoring |
| 66 | +- `test`: Adding tests |
| 67 | +- `chore`: Maintenance tasks |
| 68 | + |
| 69 | +Examples: |
| 70 | +``` |
| 71 | +feat(llm): add support for new LLM provider |
| 72 | +fix(adapter): resolve memory leak in online mode |
| 73 | +docs(readme): update installation instructions |
| 74 | +``` |
| 75 | + |
| 76 | +## Code Style |
| 77 | + |
| 78 | +- Follow PEP 8 |
| 79 | +- Use type hints where possible |
| 80 | +- Add docstrings to all public functions and classes |
| 81 | +- Keep line length under 100 characters |
| 82 | +- Use Black for automatic formatting |
| 83 | + |
| 84 | +## Testing |
| 85 | + |
| 86 | +- Write tests for new features |
| 87 | +- Ensure all tests pass before submitting PR |
| 88 | +- Aim for good test coverage |
| 89 | +- Use meaningful test names |
| 90 | + |
| 91 | +## Documentation |
| 92 | + |
| 93 | +- Update README.md if adding new features |
| 94 | +- Add docstrings to new code |
| 95 | +- Update CHANGELOG.md following Keep a Changelog format |
| 96 | +- Include examples for new functionality |
| 97 | + |
| 98 | +## Questions? |
| 99 | + |
| 100 | +Feel free to open an issue for any questions or join the discussion in [GitHub Discussions](https://github.com/Kayba-ai/agentic-context-engine/discussions). |
| 101 | + |
| 102 | +## License |
| 103 | + |
| 104 | +By contributing, you agree that your contributions will be licensed under the MIT License. |
0 commit comments