add expo doctor

[honghoangsts]

Summary by CodeRabbit

• Chores
  • Streamlined CI for pull requests with standard checkout, dependency install, and automated health checks.
  • Extended CI to run on the main branch and pull requests, using Node.js 20 for consistency.
  • Removed non-essential PR notifications to reduce noise.
  • Bumped app version to 0.0.5.

[coderabbitai]

Walkthrough

CI workflows were updated: expo-doctor workflow now runs on push and pull_request for main and uses Node.js 20. The pull-request workflow was simplified to standard steps (checkout, Node 20, yarn install, expo-doctor). package.json version was incremented from 0.0.4 to 0.0.5.

Changes

Cohort / File(s)	Summary of changes
CI workflows .github/workflows/expo-doctor.yml, .github/workflows/pull-request.yml	Updated triggers (include main on push/pull_request), replaced custom scripts with standard steps, set Node.js to v20, run expo-doctor, removed PR detail and Google Chat notification steps.
Package metadata package.json	Version bump 0.0.4 → 0.0.5; newline at EOF adjusted.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    participant GH as GitHub
    participant AR as Actions Runner
    participant Repo as Repo
    participant Node as setup-node@v4 (Node 20)
    participant Y as yarn
    participant ED as expo-doctor

    GH->>AR: pull_request event [activated]
    AR->>Repo: actions/checkout
    AR->>Node: Setup Node.js v20
    AR->>Y: Install deps (yarn install)
    AR->>ED: Run expo-doctor
    ED-->>AR: Report findings (success/failure)
    Note over AR,ED: Streamlined steps replacing custom scripts [Changed]

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump my paws on build logs bright,
Nodes hop to twenty, checks take flight.
PRs line up, clean and lean,
Expo doctors keep them green.
Version nibble: zero-dot-five,
CI fields where rabbits thrive. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title “add expo doctor” directly reflects the primary functional change of introducing the Expo Doctor step into the CI workflows and is concise and specific enough for a teammate to understand the main purpose of this pull request. It avoids unnecessary detail while clearly conveying the core update.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/update-github-action

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/pull-request.yml (1)

17-21: Use the Yarn script for consistency.

Since the repo standardizes on Yarn (see the doctor script in package.json), prefer calling yarn doctor instead of invoking npx expo-doctor directly to ensure we keep behavior centralized in the script.

-      - name: Run expo-doctor
-        run: npx expo-doctor
+      - name: Run expo-doctor
+        run: yarn doctor

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between af14673 and 88bf30b.

📒 Files selected for processing (3)

• .github/workflows/expo-doctor.yml (2 hunks)
• .github/workflows/pull-request.yml (1 hunks)
• package.json (2 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

package.json

📄 CodeRabbit inference engine (.cursor/rules/troubleshooting.mdc)

Use yarn as the project package manager (as configured in package.json)

Files:

• package.json

🧠 Learnings (1)

📚 Learning: 2025-09-25T10:42:32.852Z

Learnt from: CR
PR: saigontechnology/rn-base-project-expo#0
File: .cursor/rules/troubleshooting.mdc:0-0
Timestamp: 2025-09-25T10:42:32.852Z
Learning: Applies to package.json : Use `yarn` as the project package manager (as configured in package.json)

Applied to files:

• package.json