You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A `safe-outputs` option that redirects failure tracking issues to a different repository. Useful when the workflow's repository has issues disabled:
145
+
146
+
```yaml
147
+
safe-outputs:
148
+
failure-issue-repo: github/docs-engineering
149
+
```
150
+
151
+
See [Safe Outputs Reference](/gh-aw/reference/safe-outputs/).
152
+
142
153
### Upload Assets
143
154
144
155
A safe output capability for uploading generated files (screenshots, charts, reports) to an orphaned git branch for persistent storage. The AI calls the `upload_asset` tool to register files, which are committed to a dedicated assets branch by a separate permission-controlled job. Assets are accessible via GitHub raw URLs. Commonly used for visual testing artifacts, data visualizations, and generated documentation.
Copy file name to clipboardExpand all lines: docs/src/content/docs/reference/safe-outputs.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1232,6 +1232,18 @@ safe-outputs:
1232
1232
1233
1233
This mirrors the `noop.report-as-issue` pattern. Use this to silence noisy failure reports for workflows where failures are expected or handled externally.
Redirects failure tracking issues to a different repository. Useful when the current repository has issues disabled (e.g. `github/docs-internal`).
1238
+
1239
+
```yaml wrap
1240
+
safe-outputs:
1241
+
failure-issue-repo: github/docs-engineering
1242
+
create-issue:
1243
+
```
1244
+
1245
+
The value must be in `owner/repo` format. The `GITHUB_TOKEN` used must have permission to create issues in the target repository. When not set, failure issues are created in the current repository.
1246
+
1235
1247
### Group Reports (`group-reports:`)
1236
1248
1237
1249
Controls whether failed workflow runs are grouped under a parent "[aw] Failed runs" issue. This is opt-in and defaults to `false`.
Copy file name to clipboardExpand all lines: pkg/parser/schemas/main_workflow_schema.json
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -7198,6 +7198,12 @@
7198
7198
"default": true,
7199
7199
"examples": [false, true]
7200
7200
},
7201
+
"failure-issue-repo": {
7202
+
"type": "string",
7203
+
"description": "Repository to create failure tracking issues in, in the format 'owner/repo'. Useful when the current repository has issues disabled. Defaults to the current repository.",
"description": "Maximum number of bot trigger references (e.g. 'fixes #123', 'closes #456') allowed in output before all of them are neutralized. Default: 10. Supports integer or GitHub Actions expression (e.g. '${{ inputs.max-bot-mentions }}').",
0 commit comments