Skip to content

Say why the kit-repo auth step is dormant - #5

Open
ThisIsTJ wants to merge 1 commit into
mainfrom
docs/validate-auth-dormant
Open

ThisIsTJ wants to merge 1 commit into
mainfrom
docs/validate-auth-dormant

Conversation

@ThisIsTJ

Copy link
Copy Markdown
Collaborator

Comment-only change to validate.yml.

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.

🤖 Generated with Claude Code

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 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant