Thank you for your interest in contributing! This guide will help you get started.
Found a bug? Open an issue with:
- Clear description
- Steps to reproduce
- Expected vs actual behavior
- Environment details (Node.js version, OS, etc.)
Have an idea? Open an issue with:
- Use case description
- Proposed solution
- Alternative approaches considered
- Fix typos or unclear sections
- Add examples
- Improve code comments
- Bug fixes
- Performance improvements
- Test coverage improvements
cd npm/
npm install
npm testcd nuget/
dotnet restore
dotnet build
dotnet testcd python/
pip install -r requirements.txt
python -m pytestcd cocoapods/
pod install
# Run tests in Xcodecd android/
gradle build
gradle test- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Test thoroughly
- Commit with clear messages (
git commit -m 'Add amazing feature') - Push to your fork (
git push origin feature/amazing-feature) - Open a Pull Request
- ✅ Clear description of changes
- ✅ Reference related issues
- ✅ Include tests for new features
- ✅ Update documentation
- ✅ Follow existing code style
- JavaScript/Node.js: Follow existing conventions
- .NET/C#: Follow Microsoft C# guidelines
- Python: Follow PEP 8
- Swift: Follow Swift API Design Guidelines
- Java: Follow Google Java Style Guide
All contributions must include tests:
- Unit tests for new features
- Integration tests for API calls
- All existing tests must pass
- 📚 Documentation: https://docs.apiverve.com/ref/callingcode
- 💬 Discussions: GitHub Discussions
- 🆘 Support: https://apiverve.com/contact
This project follows the Code of Conduct. By participating, you agree to uphold this code.
By contributing, you agree that your contributions will be licensed under the MIT License.