Thank you for considering contributing to the Vapi Python Client SDK! We welcome contributions from the community.
- Fork the repository.
- Clone your fork.
- Create a new branch for your feature or fix:
git checkout -b feature/my-new-feature. - Make your changes.
- Write tests that cover your changes.
- Ensure all tests pass.
- Commit your changes using a descriptive commit message (e.g.,
feat: Add support for new webhook event). - Push your branch to your fork.
- Open a Pull Request against the
mainbranch of the original repository.
We follow the Conventional Commits specification. Please use the following prefixes:
feat: A new feature.fix: A bug fix.docs: Documentation only changes.style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc).refactor: A code change that neither fixes a bug nor adds a feature.perf: A code change that improves performance.test: Adding missing tests or correcting existing tests.build: Changes that affect the build system or external dependencies.ci: Changes to our CI configuration files and scripts.chore: Other changes that don't modify src or test files.
Thank you for helping us improve the Vapi Python Client SDK!