FEATURE REQUEST:Implement PR Build Check for Android & iOS

Abierto
#72 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@xkaper001 ya está trabajando en esto.

Desde el 22/3/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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
Lenguaje dominante
Dart
Estrellas
30
Forks
49
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AOSSIE-Org/NeuroTrack

Todos los issues de AOSSIE-Org/NeuroTrack

Issues similares

Más issues de Dart

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.