Contributing Guidelines

Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional documentation, we greatly value feedback and contributions from our community.

Please read through this document before submitting any issues or pull requests to ensure we have all the necessary information to effectively respond to your bug report or contribution.

Reporting Bugs/Feature Requests

We welcome you to use the Bug Reports file to report bugs or Feature Requests to suggest features.

For a list of known bugs and feature requests:

Check Bug Reports for currently tracked issues
See Feature Requests for requested enhancements

When filing an issue, please check for already tracked items

Please try to include as much information as you can. Details like these are incredibly useful:

A reproducible test case or series of steps
The version of our code being used (commit ID)
Any modifications you've made relevant to the bug
Anything unusual about your environment or deployment

Development Environment

This project uses hatchling as the build backend and hatch for development workflow management.

Setting Up Your Development Environment

Install development dependencies:

pip install -e ".[dev]" && pip install -e ".[litellm]

Set up pre-commit hooks:
```
pre-commit install -t pre-commit -t commit-msg
```
This will automatically run formatters and convention commit checks on your code before each commit.
Run code formatters manually:
```
hatch fmt --formatter
```
Run linters:
```
hatch fmt --linter
```
Run unit tests:
```
hatch test
```
Run integration tests:
```
hatch run test-integ
```

Pre-commit Hooks

We use pre-commit to automatically run quality checks before each commit. The hook will run hatch run format, hatch run lint, hatch run test, and hatch run cz check on when you make a commit, ensuring code consistency.

The pre-commit hook is installed with:

pre-commit install

You can also run the hooks manually on all files:

pre-commit run --all-files

Code Formatting and Style Guidelines

We use the following tools to ensure code quality:

ruff - For formatting and linting
mypy - For static type checking

These tools are configured in the pyproject.toml file. Please ensure your code passes all linting and type checks before submitting a pull request:

# Run all checks
hatch fmt --formatter
hatch fmt --linter

If you're using an IDE like VS Code or PyCharm, consider configuring it to use these tools automatically.

Contributing via Pull Requests

Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:

You are working against the latest source on the main branch.
You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
You open an issue to discuss any significant work - we would hate for your time to be wasted.

To send us a pull request, please:

Create a branch.
Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
Format your code using hatch fmt --formatter.
Run linting checks with hatch fmt --linter.
Ensure local tests pass with hatch test and hatch run test-integ.
Commit to your branch using clear commit messages following the Conventional Commits specification.
Send us a pull request, answering any default questions in the pull request interface.
Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.

Finding contributions to work on

Looking at the existing issues is a great way to find something to contribute on.

You can check:

Our known bugs list in Bug Reports for issues that need fixing
Feature requests in Feature Requests for new functionality to implement

Code of Conduct

This project has adopted the Amazon Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opensource-codeofconduct@amazon.com with any additional questions or comments.

Security issue notifications

If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our vulnerability reporting page. Please do not create a public github issue.

Licensing

See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution.