Thank you for contributing.
- Read
README.mdandSECURITY.md. - Search existing issues and pull requests before opening a new one.
- Keep changes focused and scoped.
- Install JDK 17 and Android SDK.
- Open project in Android Studio.
- Sync Gradle.
- Run:
./gradlew :app:installGithubDebug- Create feature branches from
main. - Use clear commit messages.
- Prefer small, reviewable commits.
Suggested commit style:
type(scope): short summary
Examples:
feat(settings): add support email row in contact sectionfix(player): handle null stream metadata safely
- Use Kotlin idioms and keep functions focused.
- Follow existing project style and naming.
- Avoid broad formatting-only changes unrelated to your task.
- Keep UI and behavior changes consistent with existing architecture.
Before opening a pull request:
- Build app successfully.
- Verify the changed flow manually on an emulator or device.
- Run relevant tests if added/available.
Minimum check:
./gradlew :app:assembleGithubDebug- Explain what changed and why.
- Include testing notes.
- Add screenshots for UI changes.
- Keep PR title and description clear.
- Ensure CI passes.
Use the bug report template and include:
- device and Android version
- app version/build type
- clear reproduction steps
- expected vs actual behavior
- logs or screenshots when possible
Use the feature request template and include:
- problem statement
- proposed behavior
- alternatives considered
- optional mockups or examples
Do not open public issues for sensitive vulnerabilities.
See SECURITY.md for responsible disclosure instructions.