Skip to content

Add React Doctor CI#21

Merged
baronunread merged 2 commits into
mainfrom
feat/add-react-doctor
Jul 17, 2026
Merged

Add React Doctor CI#21
baronunread merged 2 commits into
mainfrom
feat/add-react-doctor

Conversation

@baronunread

Copy link
Copy Markdown
Owner

Summary

  • Adds .github/workflows/react-doctor.yml, running React Doctor's official GitHub Action (millionco/react-doctor@v2) on every PR and on pushes to main.
  • Posts a sticky summary comment plus inline review comments on changed lines for issues newly introduced by the PR.
  • fetch-depth: 0 gives the action full git history to diff the PR against its base branch.

Test plan

  • Confirm the "React Doctor" check appears on this PR and passes (workflow-only change, no eligible React files touched).

Reports issues introduced by each pull request via a sticky summary
comment and inline review comments on changed lines.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@baronunread
baronunread force-pushed the feat/add-react-doctor branch from 54c5c0a to 4908ff1 Compare July 17, 2026 11:11
@coderabbitai

coderabbitai Bot commented Jul 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@baronunread, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 25 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 10f1a4f5-7c55-4277-9d76-cfde227b0d77

📥 Commits

Reviewing files that changed from the base of the PR and between 21f9c20 and 90e200a.

📒 Files selected for processing (1)
  • .github/workflows/react-doctor.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/add-react-doctor

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

Comment @coderabbitai help to get the list of available commands.

@baronunread
baronunread merged commit 90bc688 into main Jul 17, 2026
6 checks passed
@baronunread
baronunread deleted the feat/add-react-doctor branch July 17, 2026 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant