Repository navigation
gh-prs-merge: name a check GitHub never started, not 'test=fail' (0.68.4) - #193
Merged
Merged
Conversation
…t a failure A billing block or account lock fails every Actions job in seconds with no runner and no log. gh pr checks reports that as test=fail, so the sweep printed 'checks not green: test=fail' and sent the reader off to debug a test that never ran. The truth is only in the check run's annotation. Red checks now carry their job link; for each, the sweep reads the check-run annotations and, when GitHub says 'The job was not started because ...', appends that sentence to the skip reason and says it is billing, not code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan33 finding(s) HIGH/CRITICAL: 7 | MEDIUM: 12 | LOW: 14
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Today's sweep printed
checks not green: test=failfor cigarunderground.org#12 and mediaanalyzer.pro#16. Neither test ran: GitHub refused both jobs ("The job was not started because recent account payments have failed…"), which only shows in the check run's annotation.gh pr checksnow asks forlink;Check.linkcarries the job URL.Gh.refusedToStart()readscheck-runs/<job>/annotationsfor red Actions checks and returns the ones GitHub never started.checks not green: test=fail — GitHub never started test, so nothing was tested: "The job was not started because…" (account billing, not the code; run the gate locally and merge by hand).Verified live: against mediaanalyzer.pro#16 it returns
{names:["test"], message:"The job was not started because recent account payments have failed…"}.Tests:
test/prs-merge.test.ts55/55,tsc --noEmitclean. Full suite: 2 unrelated failures (dev2-deploy-app80s timeout under load,proxyenv coverage), not touched here.🤖 Generated with Claude Code