airqo-platform / airqo-platform/AirQo-frontend
Workflow fails to resolve Dart Code Metrics action in mobile-app-code-analysis
- Vorherrschende Sprache
- TypeScript
- Sterne
- 23
- Forks
- 48
- Ø Merge
- 15 Std. 49 Min.
- Gemergte PRs (30 T.)
- 63
Beschreibung
**What were you trying to achieve?**
Run the `mobile-app-code-analysis` GitHub Actions workflow for PR #3949 successfully.
**What are the expected results?**
The workflow should resolve the Dart Code Metrics action and proceed to metrics/analysis steps without failing during action resolution.
**What are the received results?**
The job fails immediately during workflow preparation with:
`Unable to resolve action dart-code-checker/dart-code-metrics-action[0m, not found`
The failure occurs in `.github/workflows/dart-code-metrics.yaml` in the `metrics` job at the `Dart Code Metrics Action` step.
**What are the steps to reproduce the issue?**
1. Open or run PR #3949.
2. Trigger the `mobile-app-code-analysis` workflow.
3. Observe that the `metrics` job fails before execution because GitHub cannot resolve the action reference.
**In what environment did you encounter the issue?**
- OS: GitHub Actions runner
- Version: ubuntu-latest
**Additional context**
Workflow file: `.github/workflows/dart-code-metrics.yaml`
The current step uses:
```yaml
- name: Dart Code Metrics Action
uses: dart-code-checker/dart-code-metrics-action@v4.0.0
```
This action reference appears to be invalid or unavailable, causing the workflow to fail before code analysis starts.
Suggested fix: update the step to a valid, existing Dart Code Metrics action reference and pin it to a known-good release tag.
Beitragsleitfaden
Rechercherichtung
Read .github/workflows/dart-code-metrics.yaml, starting at the metrics job's Dart Code Metrics Action step. Verify the action reference against an existing Dart Code Metrics release, update it to a known-good pinned tag, then run mobile-app-code-analysis on PR #3949 and confirm that metrics and analysis proceed without action-resolution failure.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- dart, github-actions
- Bereich
- ci-cd, mobile-dev
- Issue-Typ
- Bug
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Aktivitätsstatus
- Aktiv
- Klarheit
- Klar beschrieben
- Anfängerfreundlichkeit
- 48/100