Allow target in safe-outputs.create-check-run frontmatter schema

[Copilot]

The Go compiler parses a target field on safe-outputs.create-check-run and the safe-outputs reference documents all four targeting modes, but the frontmatter JSON schema never declared the property while setting additionalProperties: false. Any workflow copying the documented example fails to compile, with a suggestion list pointing at unrelated keys.

safe-outputs:
create-check-run:
name: "Test Check"target: "*"

• .github/workflows/t.md:10:5: error: Unknown property: target. Did you mean 'staged'?

Changes

• pkg/parser/schemas/main_workflow_schema.json — added the target string property to properties.safe-outputs.properties.create-check-run, matching the shape used by the ~27 other safe outputs that already declare it.
• pkg/parser/schema_safe_outputs_target_test.go — added a create-check-run with target case to the existing TestMainWorkflowSchema_SafeOutputsTargetProperties regression table.

The reproduction workflow now compiles, and the generated lock file gains the pull-requests: read permission the docs describe as auto-added when target is configured — previously unreachable.

Not addressed

The issue also proposes extending scripts/check-safe-outputs-conformance.sh to assert that every yaml: tag on a safe-output config struct has a matching schema property, which would catch this class of drift rather than each instance. That is a broader change and is left as a follow-up so this fix stays narrow.

• Fixescreate-check-run.target is parsed by the compiler and documented, but rejected by the frontmatter schema #53062

[pelikhan]

@copilot do this work: The issue also proposes extending scripts/check-safe-outputs-conformance.sh to assert that every yaml: tag on a safe-output config struct has a matching schema property, which would catch this class of drift rather than each instance.

[Copilot]

Pull request overview

Adds schema support for safe-outputs.create-check-run.target, aligning validation with compiler behavior and documentation.

Changes:

• Declares the target string property.
• Adds regression coverage for schema validation.

Show a summary per file

File	Description
pkg/parser/schemas/main_workflow_schema.json	Adds create-check-run.target to the schema.
pkg/parser/schema_safe_outputs_target_test.go	Verifies configurations using the property pass validation.

Review details

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Balanced

[gh-aw-bot]

@copilot PR sous-chef triage for #53113.

• Failed checks:
  • Unit tests (D-L)
  • Unit tests (M-R)
• Please address the outstanding review feedback from Copilot: Allow target in safe-outputs.create-check-run frontmatter schema #53113 (comment)
• Please refresh the branch if needed and run the pr-finisher skill before handing back.

Run: https://github.com/github/gh-aw/actions/runs/31948478139

Generated by 👨‍🍳 PR Sous Chef · gpt54 · 4.7 AIC · ⌖ 5.76 AIC · ⊞ 8.7K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot do this work: The issue also proposes extending scripts/check-safe-outputs-conformance.sh to assert that every yaml: tag on a safe-output config struct has a matching schema property, which w...

Implemented the conformance check in 4f1327b. It compares directly declared YAML fields on registered safe-output handler configs with their schema properties and now reports existing schema drift, while covering create-check-run.target.

[Copilot]

@copilot PR sous-chef triage for #53113.

• Failed checks:...

Addressed the outstanding target-semantics review in bc4ad18. Scoped validation passes; the reported prior unit-test failures reproduce in unrelated workflow validation tests and predate this correction.

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.87.1