Emit an exact-case anchor beside each STATUS.md heading - #9
Open
adamXbot wants to merge 1 commit into
Open
Conversation
GitHub lowercases generated heading anchors, so a README linking STATUS.md#AUcoverage silently missed and dropped the reader at the top of the file instead of that project's entry. Two of seventeen READMEs in the first rollout batch hit this. Emitting an explicit <a id> with the repo's real casing means both the exact and lowercased spellings resolve, so the mistake stops being possible rather than being caught by review. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 9, 2026
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.
GitHub lowercases generated heading anchors, so
STATUS.md#AUcoveragesilently misses and drops the reader at the top of the file rather than at that project's entry.Two of the seventeen READMEs in the first rollout batch hit this (AUcoverage, CyberThing-Trustmark). Both are fixed in their own PRs, but the class of bug is worth closing: every repo whose name contains a capital letter is a candidate, and the failure is silent — the link works, it just goes to the wrong place.
Emitting an explicit
<a id="<repo>"></a>with the real casing means both spellings resolve.Needs a
v1retag after merge.🤖 Generated with Claude Code