Problem
The mobile app repo has no CI workflow. A typo in any component can break the Expo build and only be discovered when EAS build fails hours later.
Context
Expo builds are slow and rate-limited. Catching compile errors at PR time via a cheap expo export --platform web is dramatically faster than waiting for an EAS run.
Before Starting
Read these context files first:
- context/architecture-context.md
- context/code-standards.md
- context/progress-tracker.md
What To Build
- Create
.github/workflows/ci.yml in StepFi-App.
- Triggers:
pull_request and push to main.
- Job
web-build: ubuntu-latest, Node 20, cache npm.
- Steps: checkout → setup-node →
npm ci → npx expo export --platform web.
- Upload web build as artifact for inspection.
- Status badge in README.
Files To Touch
.github/workflows/ci.yml
README.md
Acceptance Criteria
Mandatory Checks Before PR
Problem
The mobile app repo has no CI workflow. A typo in any component can break the Expo build and only be discovered when EAS build fails hours later.
Context
Expo builds are slow and rate-limited. Catching compile errors at PR time via a cheap
expo export --platform webis dramatically faster than waiting for an EAS run.Before Starting
Read these context files first:
What To Build
.github/workflows/ci.ymlin StepFi-App.pull_requestandpushto main.web-build: ubuntu-latest, Node 20, cache npm.npm ci→npx expo export --platform web.Files To Touch
.github/workflows/ci.ymlREADME.mdAcceptance Criteria
Mandatory Checks Before PR