aigw-contrib-pr-guide

Submitting a pull request to envoyproxy/ai-gateway requires following specific PR conventions, enforced commit formats, and mandatory import aliases. Contributors must align code or documentation changes with project expectations to pass reviews and maintain code quality.

The required commit format for envoyproxy/ai-gateway contributions enforces standardized commit messages to align submissions with project expectations. Following this specific format ensures your code or documentation changes pass the review flow and remain maintainable.

Yes, mandatory import aliases are required for ai-gateway translator contributions and all code changes. The project specifies strict alias usage rules and prohibits certain banned packages to ensure reviews pass and code remains maintainable.

Review expectations for fixing bugs in the ai-gateway include meeting API-first rules, using mandatory import aliases, and avoiding prohibited imports. Maintainers check submissions against a standardized checklist to prevent common mistakes and ensure acceptance criteria are met.

When updating docs or code for envoyproxy/ai-gateway, specific packages are banned from imports to maintain project standards. The contribution guide specifies these prohibited dependencies and documentation standards to ensure reviews pass successfully.

The API-first rule affects ai-gateway pull requests by requiring API design alignment before implementation. Contributors must follow this rule alongside commit format and import alias standards to ensure changes pass review and remain maintainable.