Aiden Bai 7db0805e98 fix(action): score step is output-only, never fail the job (#190) (#195) ...

The composite action ran the score step as `react-doctor <dir> --score`
without forwarding any `--fail-on` value, so the CLI's default
(`--fail-on error`) applied. Combined with `set -e -o pipefail`, that
killed the job whenever the score landed in the "Needs work" band even
though the diff scan had already satisfied the user's configured
`fail-on` and the score itself is the only signal the step exists for.

Two complementary fixes:

1. action.yml: the score step now always runs with `--fail-on none`
   and tolerates the pipeline failing (`|| true`). The score's value
   is the only signal — its exit code never gates the workflow.
2. CLI: `--score` is an output-collection mode. Skip the
   `shouldFailForDiagnostics` exit-code branch when `--score` is set,
   matching the documented contract that `--score` outputs only the
   score.

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Aiden Bai <aidenybai@users.noreply.github.com>

2026-05-09 21:44:42 -07:00

..

react-doctor

fix(action): score step is output-only, never fail the job (#190) (#195)

2026-05-09 21:44:42 -07:00

website

fix(website): keep diagnostic count next to rule name on narrow widths (#181)

2026-05-08 19:39:51 -07:00