From 7d9bb5ba96febfb7671f932a415926932b90582d Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Mon, 9 Mar 2026 23:54:46 +0000 Subject: [PATCH] Sync github-agentic-workflows.md with v0.40.1 Document the report-failure-as-issue safe-outputs field added in 2397829. Co-Authored-By: Claude Sonnet 4.6 --- .github/aw/github-agentic-workflows.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/aw/github-agentic-workflows.md b/.github/aw/github-agentic-workflows.md index 33ead08d9ff..24d22be6242 100644 --- a/.github/aw/github-agentic-workflows.md +++ b/.github/aw/github-agentic-workflows.md @@ -1071,6 +1071,8 @@ The YAML frontmatter supports these fields: - Patches exceeding this size are rejected to prevent accidental large changes - `group-reports:` - Group workflow failure reports as sub-issues (boolean, default: `false`) - When `true`, creates a parent `[aw] Failed runs` issue that tracks all workflow failures as sub-issues; useful for larger repositories + - `report-failure-as-issue:` - Create failure tracking issues when workflows fail (boolean, default: `true`) + - When `false`, disables automatic failure issue creation; useful when failures are expected or handled elsewhere - `id-token:` - Override the id-token permission for the safe-outputs job (string: `"write"` or `"none"`) - `"write"`: force-enable `id-token: write` permission (required for OIDC authentication with cloud providers) - `"none"`: suppress automatic detection and prevent adding `id-token: write` even when vault/OIDC actions are detected in steps