Thanks for contributing. This project keeps changes small, testable, and releasable.
- Create a branch from
main. - Run local validation:
make checkmake precommitwhen your change touches build/release paths
- Open a PR with:
- problem statement
- change summary
- test evidence (
flutter test, screenshots, or logs)
Use Conventional Commits:
feat:new behaviorfix:bug fixdocs:documentation onlyrefactor:non-behavioral code changetest:test-only changeschore:maintenance
- Keep generated code committed (
*.g.dart). - Do not introduce new analyzer debt beyond current budget.
- Keep coverage above the repository threshold.
- Avoid
print; useAppLogger. - Keep public APIs backward compatible unless explicitly planned.
- Prefer small focused PRs over large multi-topic changes.
Include:
- platform and OS version
- Flutter and Dart versions
- reproducible steps
- expected vs actual behavior
- logs or screenshots when available