docs(claude): collect the three names that are configuration - #38
Merged
Conversation
Branch protection on master now pins ci.yml's three job names as required status checks, so renaming a job leaves PRs pending forever on a check that will never report — reads like CI is down, not like a config error. That is the third instance of the same shape, alongside npm-publish.yml's filename (registered with npm) and action.yml's build chain (outputs stay populated while the files are empty). Collect all three in one table at the top rather than leaving them scattered, and record why enforce_admins is deliberately off: the release skill pushes the npm version commit straight to master, and a locally-created commit can never have passed a required check, so enforcing admins would break /release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PgfFLCcVjPxZJmMspbY4Bu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents a trap created by enabling branch protection:
ci.yml's three job names are now pinned as required status checks, so renaming a job leaves PRs pending forever on a check that never reports — which reads like CI being down rather than a config error.That is the third instance of the same shape in this repo, so all three are collected into one table at the top of CLAUDE.md instead of staying scattered:
ci.ymljob namesnpm-publish.ymlfilenameaction.ymlbuild chainAlso records why
enforce_adminsis deliberately off: thereleaseskill pushes thenpm versioncommit straight to master, and a locally-created commit can never have passed a required check, so enforcing admins would break/release.Verified the three job names match across all three places (
ci.yml, CLAUDE.md, branch protection).Docs only — no spec under
openspec/specs/touched. Also serves as the first live test of the new branch protection.