FEATURE REQUEST:Implement PR Build Check for Android & iOS

Aperta
#72 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@xkaper001 ci sta già lavorando.

Dal 22/3/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Is your feature request related to a problem?
  • Yes, it is related to a problem
Describe the feature you'd like

🌟 Feature Description

Implement a GitHub Actions workflow that automatically builds the Android and iOS versions of the Flutter app whenever a pull request (PR) is created or updated. This ensures that new changes do not break the build process before merging.

🔍 Problem Statement

Currently, there is no automated check to verify whether a PR causes build failures for Android or iOS. Without this, broken builds might get merged into the main branch, leading to debugging overhead and delays in development.

🎯 Expected Outcome

  • A GitHub Actions workflow is triggered on every PR creation or update.
  • The workflow successfully builds the Android app using flutter build apk.
  • The workflow successfully builds the iOS app using flutter build ios (on macOS runner).
  • The build process fails if any step encounters an error, preventing broken PRs from being merged.
  • Build logs are available for debugging in the GitHub Actions tab.

📷 Screenshots and Design Ideas

Workflow YAML configuration will

  • pull_request event trigger.
  • Separate jobs for Android (Linux runner) and iOS (macOS runner) to optimize resource usage.
  • Failure notifications for failed builds.

Image

Image

Image

📋 Additional Context

  • macOS runners are required for iOS builds due to Xcode dependencies.
  • Android builds can be run on Linux runners to reduce costs.
  • Future enhancements could include adding automated tests and static code analysis.
Record
  • I agree to follow this project's Code of Conduct
  • I want to work on implementing this feature
Lingua principale
Dart
Stelle
30
Fork
49
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AOSSIE-Org/NeuroTrack

Tutte le issue di AOSSIE-Org/NeuroTrack

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.