Uh oh!
There was an error while loading. Please reload this page.
[throwaway probe] fenced-code closing-keyword reading for issue 8476 step 1 - #8523
Closed
hotlong wants to merge 1 commit into
Closed
[throwaway probe] fenced-code closing-keyword reading for issue 8476 step 1#8523hotlong wants to merge 1 commit into
hotlong wants to merge 1 commit into
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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 freeto 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.
Throwaway probe opened to be READ, not merged. Empty commit, no diff. This PR and its three throwaway targets are closed immediately after the reading.
It settles one stated unknown in
scripts/pm/check-half-states.mjs:stripMarkdownCodeblanks fenced blocks as well as inline spans, but only the inline case was ever measured live. If GitHub's closing-keyword parser DOES fire inside a fence, that rule is a false negative and must be revised before a blocking check can rely on it.Three arms, one body, one moment:
Arm A — FENCED block (the unknown under test):
Arm B — INLINE code span (control, expected: no closing link):
Fixes #8521Arm C — PLAIN prose (positive control, expected: a closing link): Fixes#8522
Arm C is what makes the reading interpretable: without it, "no link on arm A" cannot be told apart from "closing links only materialize on merge".
Reading taken from
closed_by_pull_requestson each of the three targets, with this PR open and unmerged.Generated by Claude Code