Migrating to CI v2
The React Doctor GitHub Action is now v2. For most workflows, upgrading is a version bump, a deeper checkout, and a couple of renamed inputs.
Bump the Action
- uses: actions/checkout@v5
with:
fetch-depth: 0
- uses: millionco/react-doctor@v2v2 compares each pull request against its base branch, so check out with fetch-depth: 0.
Inputs that changed
| v1 | v2 |
|---|---|
fail-on | blocking |
annotations | review-comments |
non-blocking: true | blocking: none |
blocking takes the same values as fail-on (error, warning, and none) with the same error default, so a straight rename is usually all you need. A new scope input chooses between the changed files (changed, the default) and the whole project (full).
New defaults and behavior
node-versionnow defaults to24(it was22), andprojectdefaults to*, so every workspace project is scanned.- On a pull request, the Action reports only the issues your change introduced and posts inline review comments on the changed lines. A new
fixed-issuesoutput reports how many your change resolved.
See GitHub Actions setup for the full list of inputs and outputs.