Problem:
When a gh-aw agentic workflow fails, the built-in failure reporting creates issues in the current repository (context.repo). However, some repositories have issues disabled (e.g. github/docs-internal), which means the failure reporting silently fails.

Proposed solution:
Add a configuration option (e.g. failure-issue-repo) to the workflow frontmatter that lets you specify a different repository for failure issues. For example:

failure-issue-repo: github/docs-engineering

This would allow teams that have issues disabled on their main repo to redirect failure notifications to a companion repo where issues are enabled.

Current workaround:
Setting GH_AW_FAILURE_REPORT_AS_ISSUE=false and adding a custom step in the conclusion job to create issues cross-repo, but this is fragile and defeats the purpose of the built-in mechanism.

cc @Ebonsignori @heiskr @janiceilene @anjuan

— GitHub Copilot