From e11dd0ef71214b79731ba5f31225bb9773aa70a1 Mon Sep 17 00:00:00 2001 From: Tjeerd Stap <64895800+ThisIsTJ@users.noreply.github.com> Date: Thu, 27 Aug 2026 12:03:46 -0700 Subject: [PATCH] Say why the kit-repo auth step is dormant The kit repo is public, so `npm ci` clones it with no auth and no consumer defines the secret the step tests for -- it is skipped on every run today. The old comment described it as load-bearing, which sends anyone debugging a failed install down the wrong path. The step is kept rather than deleted: if the kit goes private again the default token cannot clone it and the git URL must carry one that can. Co-Authored-By: Claude Opus 5 --- .github/workflows/validate.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/validate.yml b/.github/workflows/validate.yml index 7faf23d..9dc663b 100644 --- a/.github/workflows/validate.yml +++ b/.github/workflows/validate.yml @@ -38,8 +38,10 @@ jobs: node-version: ${{ inputs.node-version }} cache: npm - # The kit lives in a private repo, so plain `npm ci` cannot clone it with - # the default token. Rewrite the git URL to carry a token that can. + # Dormant while the kit repo is public: `npm ci` clones it with no auth and + # no repo defines this secret, so the step is skipped. Kept for the case + # where the kit goes private again, when the default token cannot clone it + # and the git URL must carry one that can. # The `secrets` context is not available in a step-level `if`, so the token # is mapped to env first and the condition tests that. - name: Authenticate to the kit repo