Skip to content

Diagnose GitHub Actions billing-blocked jobs - #1117

Open
mikemikimike wants to merge 1 commit into
ProAgentStore:mainfrom
mikemikimike:fix/1112-actions-billing-diagnosis
Open

mikemikimike wants to merge 1 commit into
ProAgentStore:mainfrom
mikemikimike:fix/1112-actions-billing-diagnosis

Conversation

@mikemikimike

Copy link
Copy Markdown

Fixes #1112. Issue: #1112. When a failed Actions job never starts, GitHub check-run annotations can identify an account payment or spending-limit block. This change classifies the exact billing annotation as actions_billing_blocked and carries the original reason through job-log responses, workflow-run output, CI health reports, and notifications. Annotation access is best effort; inaccessible annotations preserve the existing failure/no-log behavior. Tests: focused Vitest (4 files, 144 passed); SDK build, 11 workspace typechecks, and changed-file Biome passed. Full suite differential: 16,816 passed / 339 failed on this branch vs 16,802 passed / 342 failed on the clean base; 335 failure assertions overlap, candidate-only failures are in an unmodified script test file, and 58 Windows spawn EFTYPE failures occur in both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Surface the exact reason when a GitHub Actions run can't start (build minutes / spending limit exhausted) instead of "completed, no log"

1 participant