chore(scaffold): M0 — Gradle + Compose + Hilt skeleton with CI #3
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/android-m0-scaffold"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
M0 — Repo scaffold
Fresh, single-commit version of the M0 scaffold (supersedes #2, whose CI iterations left a noisy history and whose runs lagged behind the workflow fixes). Stands up the Android-app repo per
docs/android/PLAN.mdM0: a buildable Kotlin + Jetpack Compose (Material 3) single-activity skeleton wired for Hilt, ready for the M1–M4 functional pass.What's here
minSdk 29,compile/target 35;applicationId com.runicgateway.app.RunicGatewayApp(@HiltAndroidApp),MainActivity(Compose),ui/theme/*; externalized strings; adaptive icon; backup rules exclude the token store / DataStore..gitea/workflows/pr-checks.yml):lint test assembleDebug, with the runner-specific fixes baked in — JDK 17 via apt (this runner can't resolveapi.adoptium.net), SDK viasdkmanager, andchmod +x gradlewin-step (the runner's checkout drops the git exec bit).Verification
Built locally against the Android Studio SDK (platform 35 + build-tools 35.0.0):
./gradlew lint test assembleDebugpasses and produces a debug APK. This PR's own first CI run is the fresh end-to-end check on the runner.AI-assisted contribution disclosure: authored with Claude Code (Claude Opus); commit carries a
Co-Authored-By: Claudetrailer.🤖 Generated with Claude Code
Pull request closed