From 58519b2447aab796d05ba43f7b7d872c5990e5df Mon Sep 17 00:00:00 2001 From: hyperpolymath <6759885+hyperpolymath@users.noreply.github.com> Date: Mon, 14 Sep 2026 21:26:24 +0100 Subject: [PATCH] fix(ci): repair unparseable scorecard.yml that startup-kills the run `permissions: read-all` was followed by an indented `actions: read`, i.e. a scalar value with a mapping key under it. That is not valid YAML: yaml: line 12, column 10: mapping values are not allowed in this context The file also carried a second, well-formed `permissions:` block immediately below the broken pair, so the malformed two lines are pure debris from a permissions sweep. Deleting them leaves the intended permissions intact. Why this matters more than a red build: the run is created, emits `jobs.total_count == 0` and NEVER produces a check run, so a *required* context simply never reports. An unrepaired repo therefore looks GREENER than a repaired one. Screen on job count, never on conclusion colour. Verified: `yq` parses; `jobs` is a non-empty map; `jobs.analysis` is a pure reusable-workflow caller (`uses` present, no `steps`, no `runs-on`); actionlint clean. The pin 8f2ee508 resolves and is left untouched. This is the same repair already carried by the other ten repos in this family; bofig was the one member with no open repair PR. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_0178nN4Nm3neFRy5K9StZKnB --- .github/workflows/scorecard.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/.github/workflows/scorecard.yml b/.github/workflows/scorecard.yml index 8aa8536..c44045e 100644 --- a/.github/workflows/scorecard.yml +++ b/.github/workflows/scorecard.yml @@ -9,8 +9,6 @@ on: push: branches: [main] -permissions: read-all - actions: read permissions: actions: read