Skip to content

Bug: workflow_install_note.md ENOENT in safe_outputs when PR touches workflow files #33622

@corygehr

Description

@corygehr

Summary

When an agentic workflow emits a create_pull_request safe-output that modifies files under .github/workflows/, the safe_outputs job crashes with:

ENOENT: no such file or directory, open '/home/runner/work/_temp/gh-aw/md/workflow_install_note.md'

The framework attempts to inject an "install note" into the PR body (or a follow-up comment) explaining that the PR contains workflow changes requiring compilation — but the template file is never deployed to the runner's temp directory.

Reproduction

  1. Create an agentic workflow that emits a create_pull_request safe-output.
  2. Have the agent include file changes under .github/workflows/ in the PR.
  3. The safe_outputs job fails at "Process Safe Outputs" with the ENOENT error.

The failure cascades: if a subsequent add_comment safe-output also references the PR, it fails with the same error (the framework prepends a "code push failure note" that re-triggers the missing template read).

Observed behavior

  • The agent job completes successfully — all reasoning and tool calls work fine.
  • The safe_outputs job fails because the framework can't read the template.
  • Both create_pull_request and any downstream add_comment that references the PR fail.
  • The conclusion job logs the error under GH_AW_CODE_PUSH_FAILURE_ERRORS.

Expected behavior

The workflow_install_note.md template should be deployed alongside other framework assets during the pre_activation or activation phase — or the framework should gracefully skip the install note if the file is absent.

Environment

  • gh-aw version: v0.74.7
  • Runner: GitHub-hosted (ubuntu-latest)
  • Workflow trigger: workflow_dispatch (slash command via centralized routing)

Workaround

None known. The only mitigation is to avoid having the agent create PRs that touch .github/workflows/ files — which defeats the purpose of workflows like Q&A or prompt-refinement that propose workflow improvements.

Impact

Any workflow that creates PRs containing .github/workflows/ file changes is broken. This affects use cases like:

  • AI-assisted workflow optimization (Q&A agents proposing prompt improvements)
  • Prompt refinement workflows that update .agent.md or .md workflow files
  • Any agent that suggests configuration changes to workflow frontmatter

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions