How Can I Contribute?

You can help with reproducible bug reports, documentation corrections, focused code changes, and tested improvements. Start with the repository responsible for the change; application and documentation contributions follow separate policies.

Contribute to the application

Read the application contribution guide before opening an issue or pull request. The current guide describes a contribution gate: issues from accounts without issue approval and pull requests from accounts without PR approval are closed automatically. Maintainers may review and reopen worthwhile issues. The tracked approved-contributor list distinguishes issue approval from PR approval; neither grants repository access.

Follow the policy's approval process rather than repeatedly reopening or duplicating a closed submission. Historical customer status alone is not a substitute for checking the project's current rules.

For code changes, read the application's AGENTS.md, keep the patch focused, and run the relevant checks required by that repository. Include what changed, why, and validation results. AI-assisted work is welcome under the contribution guide, but you should understand and be able to explain the code you submit. Do not include raw generated investigation or prompt dumps as a substitute for a clear change description.

See How to Build if you need a local development environment.

Improve the documentation

Correct an inaccurate step, explain a missing workflow, improve accessible image descriptions, or fix a broken link. Use the documentation repository's contribution guide for its process. Substantial rewrites and new sections should be discussed there first; small corrections can go directly to a focused pull request.

Edit the current documentation collection and verify instructions against application source or the relevant interface. Keep Classic archived, link shared provider facts to Providers & Models, and prefer capabilities over release-specific model lists. Include the affected page and how you checked the correction.

Not ready to write a patch?

A minimal reproduction, a precise documentation correction, or a well-scoped proposal can be useful on its own. Follow Issue and Feature Request guidance so the report reaches the right project with enough information to assess it.