Thanks for your interest in contributing! This document explains the preferred workflow and expectations to help your PR get merged quickly.
- Check existing issues to avoid duplicates.
- If you plan a large change, open an issue first to discuss the design.
- Install Flutter: https://flutter.dev/docs/get-started/install
- Get dependencies:
flutter pub get- Run the app locally:
flutter run- Follow Dart & Flutter style conventions. Run the analyzer before submitting changes:
flutter analyze- Format code with:
flutter format .- Keep changes focused and small. Write clear commit messages and PR descriptions.
- Add unit tests for logic in
lib/logic/where possible. - Add widget tests for UI in
lib/widgets/orlib/screens/. - Run tests with:
flutter test- Create a branch named like
feature/short-descriptionorfix/short-description. - Rebase or merge the target branch before opening a PR to keep history clean.
- Provide a clear PR description with motivation, what changed, and any migration steps.
- Code builds and runs locally
-
flutter analyzepasses - Code formatted (
flutter format .) - New behavior covered by tests (where applicable)
- No sensitive data or credentials
- Open an issue with reproduction steps, environment (Flutter version, device), and logs if available.
By contributing you agree that your contributions will be licensed under the project's MIT License.
Thanks — YTFL.