Problem Statement
The Schema Feature Coverage Checker workflow has been blocked 100% on every run because it produces patches targeting .github/workflows/schema-demo-*.md files, which are covered by the default protected-files policy. The workflow can never succeed in its current state.
Affected Workflow & Run IDs
Root Cause
The workflow's agent (Codex) correctly identifies schema fields not covered by existing workflows and creates demo workflow files at .github/workflows/schema-demo-<field>.md. All of these paths match the default protected-files patterns, which include all content under .github/workflows/.
Exact error (× 10 branches in run §24981796377):
Cannot create pull request: patch modifies protected files (.github/workflows/schema-demo-bots.md).
Add them to the allowed-files configuration field or set protected-files: fallback-to-issue
to create a review issue instead.
Proposed Remediation
One of two options, in order of preference:
Option 1 — Add allowed-files to the workflow frontmatter (recommended):
safe-outputs:
create-pull-request:
allowed-files:
- ".github/workflows/schema-demo-*.md"This explicitly permits the workflow to push schema demo files while maintaining protection on all other workflow files.
Option 2 — Enable fallback-to-issue:
safe-outputs:
create-pull-request:
protected-files:
fallback-to-issue: trueThis creates review issues instead of blocked PRs, which is less ideal since the primary goal is to open PRs.
Success Criteria
Parent Report
Part of investigation report #28673.
Generated by [aw] Failure Investigator (6h) · ● 882.3K · ◷
Problem Statement
The Schema Feature Coverage Checker workflow has been blocked 100% on every run because it produces patches targeting
.github/workflows/schema-demo-*.mdfiles, which are covered by the defaultprotected-filespolicy. The workflow can never succeed in its current state.Affected Workflow & Run IDs
Schema Feature Coverage Checker(workflow ID:schema-feature-coverage)Root Cause
The workflow's agent (Codex) correctly identifies schema fields not covered by existing workflows and creates demo workflow files at
.github/workflows/schema-demo-<field>.md. All of these paths match the defaultprotected-filespatterns, which include all content under.github/workflows/.Exact error (× 10 branches in run §24981796377):
Proposed Remediation
One of two options, in order of preference:
Option 1 — Add
allowed-filesto the workflow frontmatter (recommended):This explicitly permits the workflow to push schema demo files while maintaining protection on all other workflow files.
Option 2 — Enable
fallback-to-issue:This creates review issues instead of blocked PRs, which is less ideal since the primary goal is to open PRs.
Success Criteria
GH_AW_CODE_PUSH_FAILURE_COUNT= 0 on the next run.github/workflows/schema-demo-<field>.mdParent Report
Part of investigation report #28673.