Description
The safe-output config struct carries a dead, misleading yaml tag. The schema key and handler are singular create-code-scanning-alert (main_workflow_schema.json:6787, safe_output_handlers.go:218), and parsing is done via manual map access — create_code_scanning_alert.go:24 reads outputMap["create-code-scanning-alert"]. But the struct field uses a plural yaml tag:
compiler_types.go:648 CreateCodeScanningAlerts *CreateCodeScanningAlertsConfig `yaml:"create-code-scanning-alerts,omitempty"`
Because the struct is never unmarshaled directly (manual map access only), the plural create-code-scanning-alerts yaml tag is dead and contradicts the singular key used everywhere else.
Expected Impact
Removes a misleading dead tag that could trip up future maintainers who assume yaml unmarshaling honors it. Zero runtime behavior change.
Acceptance Criteria
- The yaml tag is corrected to singular
create-code-scanning-alert (or removed if truly unused), consistent with the schema/handler/parser.
go build ./... and existing tests pass.
Suggested Agent
Dead Code Removal Agent / Schema Consistency agent.
Estimated Effort
Fast (< 30 min)
Data Source
DeepReport 2026-06-05 — Schema Consistency Check #37077 (Standing Issue #2). Verified at HEAD: compiler_types.go:648 has the plural tag.
Generated by 🔬 DeepReport - Intelligence Gathering Agent · 178.3 AIC · ◷
Description
The safe-output config struct carries a dead, misleading yaml tag. The schema key and handler are singular
create-code-scanning-alert(main_workflow_schema.json:6787,safe_output_handlers.go:218), and parsing is done via manual map access —create_code_scanning_alert.go:24readsoutputMap["create-code-scanning-alert"]. But the struct field uses a plural yaml tag:Because the struct is never unmarshaled directly (manual map access only), the plural
create-code-scanning-alertsyaml tag is dead and contradicts the singular key used everywhere else.Expected Impact
Removes a misleading dead tag that could trip up future maintainers who assume yaml unmarshaling honors it. Zero runtime behavior change.
Acceptance Criteria
create-code-scanning-alert(or removed if truly unused), consistent with the schema/handler/parser.go build ./...and existing tests pass.Suggested Agent
Dead Code Removal Agent / Schema Consistency agent.
Estimated Effort
Fast (< 30 min)
Data Source
DeepReport 2026-06-05 — Schema Consistency Check #37077 (Standing Issue #2). Verified at HEAD:
compiler_types.go:648has the plural tag.