Thank you for considering contributing to Agentex! Contributions make the open source community amazing and help improve the project for everyone. Any contributions you make are greatly appreciated.
We welcome bug fixes, enhancements, documentation improvements, tests, and more.
To set up your development environment for Agentex, please refer to the README.md for up-to-date instructions.
- Fork the repository.
- Clone your fork:
git clone https://github.com/<your-username>/agentex.git cd agentex
- Set the original repo as upstream (recommended):
git remote add upstream https://github.com/scaleapi/agentex.git
- Create a new branch for your feature or bugfix:
git checkout -b my-feature-or-bugfix
- Make your changes.
Follow project coding style and conventions. - Test your changes:
Run linter/formatter as required:
make testmake lint
- Commit your changes (see commit message guidelines below).
- Push to your fork:
git push origin my-feature-or-bugfix
- Open a Pull Request against
mainwith a clear description.
This project enforces Conventional Commits on PR titles. A CI check will validate your PR title before it can be merged.
Format: type: description or type(scope): description
Allowed types: feat, fix, docs, style, refactor, test, chore, ci, build, perf, revert
Examples:
feat: add user authentication middleware
fix(api): handle empty request body gracefully
docs: update contributing guidelines
chore: bump dependency versions
- Use the imperative mood (e.g., “Add feature” not “Added feature”).
- Keep the subject line under 72 characters.
- Use the body to explain what and why vs. how (if needed).
- Reference relevant issues/PRs (e.g.,
Fixes #123).
For more, see: Chris Beams' guide to writing great commit messages.
If you want to contribute to the Agentex Python SDK, please use the scale-agentex-python repository and follow its contributing guidelines.
Be respectful and considerate. By participating in this project, you agree to abide by the Code of Conduct (if present).
If you have any questions, please open an issue or join the discussion on GitHub. We're happy to help!