Claude Code 3a04a70570 ci(tessl-review): distinguish tooling failures from low scores ...

When the Tessl CLI fails to run at all — auth failure, network error,
crash — the job counted it as a review failure and reported it as
"N skill(s) scored below 80%". That is misleading: the skill was never
scored. On adobe/skills#189 this surfaced as a red "below 80%" check on
a skill that actually scores 85%, which reads to a contributor as a
quality rejection.

Track those separately as errors and report them as "review could not be
run", with a ⚠️ row and an explanatory note in the step summary. They
still fail the job — they are just no longer confused with low scores.

Also:

- Skip cleanly with an explanatory summary when TESSL_TOKEN is not
  configured, instead of running an unauthenticated CLI and failing.
- Pin actions/checkout and tesslio/setup-tessl to commit SHAs, with
  `# vN` comments so Renovate keeps tracking them.
- Add a concurrency group so superseded runs are cancelled.
- Use a single redirect block in the skip summary, silencing the one
  actionlint/shellcheck warning (SC2129) in this file.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Lars Trieloff <lars@trieloff.net>

2026-08-21 12:41:08 +02:00

..

workflows

ci(tessl-review): distinguish tooling failures from low scores

2026-08-21 12:41:08 +02:00

CODEOWNERS

feat(commerce): add commerce-app-review plugin (#302)

2026-08-20 19:28:52 +02:00