Thank you for your interest in contributing! This document provides guidelines and information for contributors.
- Fork the repository and clone it locally
- Create a branch for your changes:
git checkout -b feature/your-feature-name - Make your changes following our coding standards
- Test your changes thoroughly
- Commit your changes with clear, descriptive messages
- Push to your fork and submit a pull request
- Docker (recommended) or your tech stack's runtime
- Git
- Install VS Code and the Dev Containers extension
- Open the project in VS Code
- Click "Reopen in Container" when prompted
python -m venv venv
source venv/bin/activate # or `venv\Scripts\activate` on Windows
pip install -r requirements.txt
uvicorn main:app --reloadnpm install
npm run devgo mod download
go run main.godotnet restore
dotnet run- Follow the existing code style
- Write meaningful commit messages
- Keep changes focused and atomic
- Add tests for new features
- Follow PEP 8
- Use type hints
- Run
ruff check .andblack .before committing
- Use ESLint and Prettier
- Run
npm run lintbefore committing
- Run
go fmtandgolangci-lint runbefore committing
- Follow Microsoft's C# coding conventions
- Ensure your PR description clearly describes the problem and solution
- Link any related issues
- Update documentation if needed
- Ensure all CI checks pass
- Request review from maintainers
type: brief description
Types: feat, fix, docs, style, refactor, test, chore
Examples:
feat: add user authenticationfix: resolve database connection timeoutdocs: update API documentation
When reporting issues, please include:
- A clear description of the problem
- Steps to reproduce
- Expected vs actual behavior
- Environment details (OS, versions, etc.)
- Relevant logs or screenshots
Feel free to open an issue for questions or discussions.