Thank you for your interest in contributing to Cohere's OSS toolkit. This guide will help explain the contribution workflow from opening an issue, creating a PR, to reviewing and merging your added changes. For development setup, please refer to the README.
Remember that there are many ways to contribute other than writing code: writing tutorials or blog posts, improving the documentation, and submitting bug reports.
- You're familiar with GitHub and the Pull Requests (PR) workflow.
- You've read the Cohere's documentation.
- You know about the Cohere community on Discord.
- Ensure your change has an issue! Find an existing issue or open a new issue.
- This is where you can get a feel if the change will be accepted or not.
- Once approved, fork this repository repository in your own GitHub account.
- Fork this repository
- Make your changes on your fork and make sure all your commits are signed!
- Submit the fork as a Pull Request pointing to the
main
branch this repository. A maintainer should comment and/or review your Pull Request within a few days. Although depending on the circumstances, it may take longer.
All features must be added to the community
folder. That's where you'll find tools and deployments that are not managed by Codeowners.