Migrating to CI v2
Upgrade a v1 workflow to the v2 Action, then review the new advisory gate and pull request scopes.
Bump the Action
Let the CLI update the workflow:
npx react-doctor@latest ci upgradeTo open the change as a pull request, add --pr. You can also edit the workflow manually:
- uses: actions/checkout@v5
- uses: millionco/react-doctor@v2Keep fetch-depth: 0 so React Doctor can always resolve the merge base. A shallow checkout can fall back to reporting every issue in changed files when the base commit is unavailable.
Inputs that changed
| v1 | v2 |
|---|---|
fail-on | blocking |
annotations | review-comments |
non-blocking: true | blocking: none |
blocking takes error, warning, or none. The v2 default is none, so new workflows report findings without failing. Set blocking: error if the v1 workflow enforced an error gate.
The new scope input accepts changed, files, lines, or full. Its default is changed, which reports only issues introduced by the pull request.
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 the GitHub Action reference for the full list of inputs and outputs.