android-workflow-internal_skill

Overview

This skill generates two focused GitHub Actions workflows for Android: a CI-only build & test workflow and a manual release workflow for the Play Store internal track. It follows Option D (Split Workflows) to enforce separation of concerns, version management, and intentional releases. The workflows integrate Gradle, JDK setup, caching, Fastlane deployment, and automated version bumping and tagging.

How this skill works

It creates .github/workflows/build.yml that runs on pushes and pull requests to main and performs checkout, JDK setup, Gradle cache/setup, assembleRelease, unit tests, and uploads test reports. It also creates .github/workflows/release-internal.yml triggered only by workflow_dispatch to perform a controlled release: calculate and commit version bumps, build the release bundle, decode keystore from secrets, run Fastlane deploy_internal, upload artifacts, create a git tag, and write a release summary. Both workflows include validation and cleanup steps.

When to use it

• You want strict separation between CI validation and deployments
• You need manual, auditable releases to the Play Store internal track
• You require automated version bumping and tag creation during releases
• You have Fastlane and version scripts already configured
• You want faster CI runs without deployment overhead

Best practices

• Ensure Fastlane setup and metadata exist before enabling workflows
• Store signing keys and service account JSON in repository secrets (base64 as needed)
• Keep fetch-depth: 0 in release workflow to allow tagging and version calculation
• Validate YAML syntax with yamllint after creating workflows
• Run bundle exec fastlane lanes locally to confirm deploy_internal lane exists

Example use cases

• Run build.yml on every PR to catch regressions and upload test reports
• Trigger Release to Internal Track manually when a new internal tester build is needed
• Use version bump input (patch/minor/major) to control semantic versioning during release
• Automate tag creation and push version commit as part of release audit trail
• Upload AAB artifacts for QA while preventing accidental public deployments