Contributing

We welcome contributions from the community! Whether it's fixing a bug, adding a new provider, or improving documentation, your help makes Quotio better.

Code of Conduct

Please be respectful and professional in all interactions. We adhere to a standard Code of Conduct suitable for professional open-source projects.

Development Workflow

1. Fork the repository on GitHub.
2. Clone your fork locally.
3. Create a Feature Branch (git checkout -b feature/my-new-provider).
4. For backend changes, work on CLIProxyAPI repository first.
5. Make your changes.
6. Run tests (go test for CLIProxyAPI backend, xcodebuild test for frontend).
7. Commit with clear messages (Conventional Commits preferred).
8. Push to your fork and submit a Pull Request.

Reporting Bugs

When filing an issue, please include:

• Version: The version of Quotio you are running.
• OS: macOS version.
• Steps to Reproduce: Clear steps to trigger the bug.
• Logs: Relevant snippets from ~/Library/Logs/Quotio/app.log (sanitize API keys!).

Documentation

License

By contributing, you agree that your contributions will be licensed under the project's MIT License.

Next Steps

Check the GitHub Issues for "good first issue" tags to get started.