-
Notifications
You must be signed in to change notification settings - Fork 0
R2.1.0 #62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
R2.1.0 #62
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
38b723b
Feat/android 17 (#59)
Devasy d386bbe
Upgrades bottom nav bar Upgrade Bottom Navigation Bar (#61)
Devasy 39fbb5e
Feat/increase coverage test screens (#63)
Devasy f85410d
Feat/genui (#64)
Devasy 41513a9
Merge branch 'main' of https://github.com/Devasy/RepForge into r2.1.0
Devasy a6f864d
Merge branch 'main' of https://github.com/Devasy/RepForge into r2.1.0
Devasy 0bd4559
Merge remote-tracking branch 'origin/main' into r2.1.0
Devasy 74c017b
test: drop coverage for ApiService/SettingsScreen removed by main merge
Devasy 8173039
Migrate storage from Hive to SQLite + add coach SQL query tool (#66)
Devasy 2cc2d23
feat: recovery-aware recommendation engine + per-model Gemini thinkin…
Devasy a8bc45a
chore: update release workflow to remove debug info from APK build
Devasy 00984c1
fix: improve text color contrast for success and error snackbars
Devasy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| # Codecov Configuration for RepForge (Devasy/RepForge) | ||
| codecov: | ||
| require_ci_to_pass: yes | ||
|
|
||
| coverage: | ||
| precision: 2 | ||
| round: down | ||
| range: "70...100" | ||
|
|
||
| status: | ||
| project: | ||
| default: | ||
| target: auto | ||
| threshold: 1% | ||
| patch: | ||
| default: | ||
| target: auto | ||
|
|
||
| ignore: | ||
| - "**/*.g.dart" | ||
| - "**/*.freezed.dart" | ||
| - "workout-logger/test/**/*" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,20 +2,31 @@ name: Test | |
|
|
||
| on: | ||
| push: | ||
| branches: [main] | ||
| branches: | ||
| - main | ||
| - 'r[0-9]+.[0-9]+.*' | ||
| pull_request: | ||
| branches: [main] | ||
| branches: | ||
| - main | ||
| - 'r[0-9]+.[0-9]+.*' | ||
| release: | ||
| types: [published] | ||
|
|
||
| concurrency: | ||
| group: ${{ github.workflow }}-${{ github.ref }} | ||
| cancel-in-progress: ${{ github.event_name == 'pull_request' }} | ||
|
|
||
| jobs: | ||
| test: | ||
| name: Analyze & Test | ||
| runs-on: ubuntu-latest | ||
|
|
||
| permissions: | ||
| contents: read | ||
|
|
||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v6 | ||
| uses: actions/checkout@v7 | ||
|
|
||
| - name: Set up Flutter | ||
| id: flutter-action | ||
|
|
@@ -28,13 +39,14 @@ jobs: | |
| pub-cache-key: "flutter-pub-:os:-:channel:-:version:-:arch:-${{ hashFiles('workout-logger/pubspec.lock') }}" | ||
|
|
||
| - name: Install dependencies | ||
| if: steps.flutter-action.outputs.PUB-CACHE-HIT != 'true' | ||
| if: steps.flutter-action.outputs.CACHE-HIT != 'true' | ||
| working-directory: ./workout-logger | ||
| run: flutter pub get | ||
|
|
||
| - name: Analyze | ||
| working-directory: ./workout-logger | ||
| run: | | ||
| set -o pipefail | ||
| # Only fail on errors, ignore warnings and info messages | ||
| flutter analyze --no-fatal-infos --no-fatal-warnings | tee analyze_output.txt | ||
|
|
||
|
|
@@ -53,3 +65,5 @@ jobs: | |
| with: | ||
| files: workout-logger/coverage/lcov.info | ||
| token: ${{ secrets.CODECOV_TOKEN }} | ||
| slug: Devasy/RepForge | ||
|
|
||
|
Comment on lines
+68
to
+69
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win Remove the added empty line. The configured YAML linter rejects the empty line after 🧰 Tools🪛 YAMLlint (1.37.1)[error] 69-69: too many blank lines (1 > 0) (empty-lines) 🤖 Prompt for AI AgentsSource: Linters/SAST tools |
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: Devasy/RepForge
Length of output: 3559
🌐 Web query:
subosito flutter-action flutter analyze test cache true outputs CACHE-HIT💡 Result:
The
subosito/flutter-actionGitHub Action providesCACHE-HITandPUB-CACHE-HIToutputs that allow you to determine whether the Flutter SDK or pub dependencies were successfully retrieved from the cache [1][2][3]. These outputs are available starting from versionv2.21.0[2]. They directly reflect thecache-hitoutput from the underlyingactions/cachesteps [4][5][3]. Key details regarding these outputs: -CACHE-HIT: Indicates whether the Flutter SDK cache was a hit [1][3]. -PUB-CACHE-HIT: Indicates whether the pub dependencies cache was a hit [1][3]. - Behavior: These outputs return'true'if there is an exact match for the cache key, and an empty string if there is a cache miss [4][6][5]. Example usage: You can use these outputs to conditionally execute steps in your workflow, such as skipping dependency installation when a cache hit occurs [7][3]: steps: - name: Set up Flutter uses: subosito/flutter-action@v2 id: flutter-action with: channel: stable cache: true - name: Conditionally run dependencies installation if: steps.flutter-action.outputs.PUB-CACHE-HIT!= 'true' run: flutter pub get - name: Continue with build run: flutter build apk Note that you must provide anidto theflutter-actionstep (e.g.,id: flutter-action) to reference these outputs in subsequent steps [7][3].Citations:
🌐 Web query:
site:github.com/subosito/flutter-action action.yaml CACHE-HIT PUB-CACHE-HIT cache💡 Result:
In the context of the subosito/flutter-action GitHub Action, CACHE-HIT and PUB-CACHE-HIT are output variables that provide information about the status of the Flutter SDK and Dart pub dependencies caches, respectively [1][2]. These outputs are defined in the action's configuration (action.yaml) to allow users to conditionally execute steps based on whether a cache was restored successfully [1][2]. Specifically: CACHE-HIT: Indicates whether the Flutter SDK cache was a hit (returns 'true' if there is an exact match for the cache key) [1]. PUB-CACHE-HIT: Indicates whether the Dart pub dependencies cache was a hit (returns 'true' if there is an exact match for the cache key) [1]. These values are sourced directly from the cache-hit output of the underlying actions/cache step used within the action [3][4]. They are commonly used in workflow YAML files to skip redundant installation or setup steps, such as bootstrapping dependencies, when a valid cache already exists [2][5]. Example usage in a workflow: - name: Set up Flutter uses: subosito/flutter-action@v2 id: flutter-action with: cache: true pub-cache: true - name: Conditionally run setup if: steps.flutter-action.outputs.PUB-CACHE-HIT!= 'true' run: dart pub get
Citations:
🌐 Web query:
site:docs.dart.dev packages flutter test analyze package_config.json pub cache💡 Result:
Relevant official Dart/Flutter documentation:
pubspec.yamlanddart pub getto resolve dependencies. [1]flutter pub,flutter analyze, andflutter test; Flutter recommends these instead of the equivalent Dart commands in Flutter projects. [2]dart analyze [DIRECTORY|FILE]analyzes Dart source code. [3]test/; run them withflutter test. [4]package_config.json: Pub generates.dart_tool/package_config.json, mapping package names to their locations; workspaces use one shared file. [5]dart pub cache gcto remove packages no longer referenced by current projects. [6]The original query returned no exact
docs.dart.devmatch; current documentation is primarily ondart.devanddocs.flutter.dev.Run dependency resolution when the Flutter SDK cache hits.
CACHE-HITreports whether the Flutter SDK cache was restored. This skipsflutter pub geteven when the project pub cache was not restored, leaving.dart_tool/package_config.jsonunresolved forflutter analyzeandflutter test. Checksteps.flutter-action.outputs.PUB-CACHE-HITinstead, or always runflutter pub getfor clean runners.🤖 Prompt for AI Agents