android-workflow-internal

To set up GitHub Actions for Android CI and internal Play Store releases, you can generate split workflows that separate build and test tasks from manual internal deployment using Fastlane. This approach creates build.yml and release-internal.yml files to automate PR checks and controlled deployments.

Split GitHub Actions workflows for Android deployments separate the CI process from the internal release flow, reducing the risk of accidental automatic deployments. This ensures reliable build testing on pull requests while maintaining a controlled, manual deployment path to the Google Play internal track.

Yes, you need Fastlane to deploy an Android app to the Play Store internal track via GitHub Actions. The generated release-internal.yml workflow relies on Fastlane for deployment and includes pre-checks to verify that Fastlane setup and metadata are correctly configured before running.

No, you cannot use this workflow with an Android project that does not use Gradle. The solution specifically requires a Gradle-based Android project to generate the CI and internal release workflows for building, testing, and deploying your application.

To generate a release-internal.yml file for your Android app, use the Skill with your app package name like com.example.myapp. It automatically outputs the internal release workflow with Fastlane pre-checks to the .github/workflows directory for controlled Play Store deployments.