# Contributing Guidelines
## How to Contribute
1. Fork the repository
2. Create your feature branch (`git checkout -b feature/AmazingFeature`)
3. Commit your changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request
## Code Style
- For backend and wails related changes follow Go standards and conventions
- For frontend changes follow Javascript ESM standards and conventions
- Use clear, descriptive variable names
- Comment complex logic
- Write tests for new features
## Pull Request Process
1. Update documentation as needed
2. Add tests for new features
3. Ensure all tests pass
4. Request review from maintainers
## Code of Conduct
- Be respectful and inclusive
- Focus on constructive feedback
- Help others learn and grow
## Release Cycle
The software release cycle uses these conventions:
- New features are developed in a new branch (`feature/xxxx`)
- Once a feature is complete, a new pull request is opened and merged into `develop`
- Once roadmap features are ready, a new release branch is created from `develop` (`release/x.y.z`)
- In the new release branch, once all tests pass, a new pull request is opened and merged into `main`
- When a new release is merged into `main`, a release tag is created with the final binaries