Versioned API schema
GitHub REST API code scanning alerts language javascript-typescript enum
Automation rejects `javascript-typescript` because it only knows separate enum values.
Agent Quick Fix
Repair against the current GitHub REST API contract, then keep the change narrow and source-backed.
Product: GitHub REST API
Current-contract area: Code scanning language enum merges JavaScript and TypeScript
Likely root cause: Automation rejects `javascript-typescript` because it only knows separate enum values.
Repair direction: Verifier exercises the changed field/status/enum plus an unaffected endpoint to prevent a brittle one-off patch. Exercise strict and permissive parsing plus one downstream behavior tied to the changed field.Symptom
Automation rejects `javascript-typescript` because it only knows separate enum values.
Why This Happens
Several historical response shapes are locally plausible; only the selected current API version determines fields, enums, media types, and status codes.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
GitHub REST API code scanning alerts language javascript-typescript enum
site:docs.github.com code scanning default setup language javascript-typescript API
"javascript-typescript" "code-scanning" "GitHub"
"javascript-typescript" "openapi" "github"
GitHub CodeQL default setup languages javascript-typescript REST API
github rest api code scanning set default setup language parameter
"CodeQL" "javascript-typescript" "REST API"Source Trail
GitHub source file/reference: