chore(mobile-expo): CI lint, typecheck, and build for Expo app#191
chore(mobile-expo): CI lint, typecheck, and build for Expo app#191
Conversation
Add a dedicated lint-expo job to the CI workflow that runs ESLint, TypeScript type checking, and build validation for the Expo app (mobile/expo) when changes are detected via Turbo affected analysis. - Extend affected job to detect @forge/expo changes - Exclude @forge/expo from main build-and-test lint step - Add conditional lint-expo job with lint, typecheck, and build steps Resolves #96 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
lint-expoCI job that runs ESLint (--max-warnings=0), TypeScript typecheck (tsc --noEmit), and build validation for the Expo app (mobile/expo)affectedjob to detect@forge/expochanges via Turbo affected analysis@forge/expofrom mainbuild-and-testlint step to avoid double-lintingResolves #96
Contracts Changed
No
Regeneration Required
No
Validation
lint-expojob follows existinglint-ios/lint-androidpattern@forge/expobeing affected (no wasted CI minutes)