Repository navigation
docs: gotcha 27's fifth sighting, and the command that hides it - #314
Merged
Merged
Conversation
#313 was CSS-only and failed `github-advanced-security` with the artifact's whole signature: title null, empty summary, one annotation, CodeQL green. Two things it added beyond the tally. The annotation sat at `.github:213`, the SAME line as #307 on a diff sharing no content with it, so the line number is a fingerprint of the harness rather than a location — do not go looking for what lives there. And `gh pr checks` did not list the failing check AT ALL: seven rows, every one pass or skipping, while `/commits/<sha>/check-runs` reported that same check as failure on the same head commit. Reproduced twice minutes apart, so it is not a timing gap. That matters because the convenient command reports the PR green while the notification says a check failed, which reads exactly like a stale alert and is not one. The `check-runs` call the note already recommends is the source of truth for this check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
aadhar-sh | c44f879 | Aug 10 2026, 08:08 PM |
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
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.
#313 was a CSS-only change and failed
github-advanced-securitycarrying the artifact's whole signature:output.titlenull, empty summary, one annotation,COPILOT_JOB_NONCEin the job log, and CodeQL reporting "No new alerts in code changed by this pull request." That is the fifth sighting, after #289, #295, #305 and #307.Two things it added beyond incrementing the tally.
The annotation line is a fingerprint, not a location. #313's lone annotation sat at
.github:213— the same line as #307, on a diff sharing no content with it. A line number that repeats across two unrelated PRs is a property of the harness, so read it as one more signature and never go looking for what lives there.gh pr checksdoes not list the failing check at all, which is the part that changes how you look. On #313 it printed seven rows, every onepassorskipping, with nogithub-advanced-securityamong them:while
/commits/<sha>/check-runsreported that same check asfailureon the same head commit. Reproduced twice minutes apart, so it is not a timing gap. The consequence is that the convenient command reports the PR green while the notification says a check failed, which reads exactly like a stale alert and is not one. Thecheck-runscall the note already recommends is the source of truth for this check;gh pr checksstays fine for everything else.Documentation only —
CLAUDE.md, whichAGENTS.mdsymlinks to. 206/206 contract tests.🤖 Generated with Claude Code