Thank you for your interest in contributing! Please follow these guidelines when submitting changes.
All commits, especially PR titles, should follow the Conventional Commits specification:
feat:- New featuresfix:- Bug fixesdocs:- Documentation changeschore:- Maintenance tasksrefactor:- Code refactoringtest:- Test additions or changesci:- CI/CD changes
Example: feat: add support for batch uploads
Always reference the related GitHub issue in your PR description using keywords like Fixes #123 or Closes #456.
For user-facing changes or CLI flows, include:
- Screenshots for UI changes
- Terminal output for CLI commands
- Before/after comparisons when relevant
Leave your PR in draft status until it's ready for maintainer review. This helps maintainers prioritize their time.
Keep comments concise and favor self-documenting code when possible. Use clear variable names, function names, and code structure to make your intent obvious.