Add approval list of files when creating a PR

[v1v]

Support https://github.github.com/gh-aw/reference/safe-outputs-pull-requests/#restricting-changes-to-specific-files-with-allowed-files

in the existing GH agentic workflows using the create-pull-requests safe output, it should be optional and managed through inputs, so providing the list of files as a string should honour the allowed-files

[github-actions]

tl;dr: This should be implemented by adding a new optional workflow input (for example allowed-files) to every PR-creating gh-aw workflow, then wiring it once in .github/workflows/gh-aw-fragments/safe-output-create-pr.md into safe-outputs.create-pull-request.allowed-files; this is the smallest complete change with safe defaults.

Recommendation

Add an optional string input (default "") for allowed files on all workflows that can call create_pull_request, and wire it centrally in safe-output-create-pr.md. Keep behavior backward-compatible by leaving current behavior unchanged when the input is empty.

Also update chained examples/docs so users can forward the input to gh-aw-create-pr-from-issue (otherwise the feature will exist but be hard to discover/use).

Findings

• PR creation safe-output config is centralized and currently does not include allowed-files: .github/workflows/gh-aw-fragments/safe-output-create-pr.md:125-128.
• The same fragment already consumes workflow inputs (draft: ${{ inputs.draft-prs }}), so input-based wiring is already the established pattern: .github/workflows/gh-aw-fragments/safe-output-create-pr.md:127.
• The workflows currently importing this fragment (and therefore needing the new input declared in workflow_call.inputs) are:
  • .github/workflows/gh-aw-create-pr-from-issue.md:15
  • .github/workflows/gh-aw-issue-fixer.md:14
  • .github/workflows/gh-aw-mention-in-issue-by-id.md:15
  • .github/workflows/gh-aw-mention-in-issue-no-sandbox.md:15
  • .github/workflows/gh-aw-mention-in-issue.md:15
  • .github/workflows/gh-aw-release-update.md:11
  • .github/workflows/gh-aw-scheduled-fix.md:12
  • .github/workflows/gh-aw-small-problem-fixer.md:12
• Consumer chaining docs/examples currently only pass target-issue-number, so they would not demonstrate forwarding an allowlist:
  • docs/workflows/detector-fixer-chaining.md:30,87,116,143
  • gh-agent-workflows/bug-hunter/example-chained.yml:22
  • gh-agent-workflows/code-complexity-detector/example-chained.yml:24
  • gh-agent-workflows/code-duplication-detector/example-chained.yml:24
  • gh-agent-workflows/newbie-contributor-patrol/example-chained.yml:22
  • gh-agent-workflows/test-coverage-detector/example-chained.yml:22
• Related prior allowlist incident: issue [bug-hunter] PR Review (RO) helper script allowlist does not match runtime path #831 and PR fix(pr-review): allow RO helper scripts via runtime-safe allowlist paths #832 (different surface, but relevant precedent that allowlist wiring needs to be precise).

Verification

I ran targeted checks in this repo:

### Check 1: No existing allowed-files wiring
# (no matches)

### Check 2: Workflows importing safe-output-create-pr fragment
.github/workflows/gh-aw-create-pr-from-issue.md:15:  - gh-aw-fragments/safe-output-create-pr.md
.github/workflows/gh-aw-issue-fixer.md:14:  - gh-aw-fragments/safe-output-create-pr.md
.github/workflows/gh-aw-mention-in-issue-by-id.md:15:  - gh-aw-fragments/safe-output-create-pr.md
.github/workflows/gh-aw-mention-in-issue-no-sandbox.md:15:  - gh-aw-fragments/safe-output-create-pr.md
.github/workflows/gh-aw-mention-in-issue.md:15:  - gh-aw-fragments/safe-output-create-pr.md
.github/workflows/gh-aw-release-update.md:11:  - gh-aw-fragments/safe-output-create-pr.md
.github/workflows/gh-aw-scheduled-fix.md:12:  - gh-aw-fragments/safe-output-create-pr.md
.github/workflows/gh-aw-small-problem-fixer.md:12:  - gh-aw-fragments/safe-output-create-pr.md

### Check 3: Current create-pull-request config in shared fragment
125:  create-pull-request:
126:    patch-format: bundle
127:    draft: ${{ inputs.draft-prs }}
128:    github-token-for-extra-empty-commit: ${{ secrets.EXTRA_COMMIT_GITHUB_TOKEN }}

### Check 4: Chaining docs/examples only pass target-issue-number today
docs/workflows/detector-fixer-chaining.md:30:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
docs/workflows/detector-fixer-chaining.md:87:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
docs/workflows/detector-fixer-chaining.md:116:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
docs/workflows/detector-fixer-chaining.md:143:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
gh-agent-workflows/bug-hunter/example-chained.yml:22:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
gh-agent-workflows/code-complexity-detector/example-chained.yml:24:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
gh-agent-workflows/code-duplication-detector/example-chained.yml:24:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
gh-agent-workflows/newbie-contributor-patrol/example-chained.yml:22:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}
gh-agent-workflows/test-coverage-detector/example-chained.yml:22:      target-issue-number: ${{ needs.detect.outputs.created_issue_number }}

Detailed Action Plan

1. Add a new optional workflow_call input (e.g., allowed-files) with default "" to each workflow that imports safe-output-create-pr.md:
   • .github/workflows/gh-aw-create-pr-from-issue.md
   • .github/workflows/gh-aw-mention-in-issue.md
   • .github/workflows/gh-aw-mention-in-issue-no-sandbox.md
   • .github/workflows/gh-aw-mention-in-issue-by-id.md
   • .github/workflows/gh-aw-issue-fixer.md
   • .github/workflows/gh-aw-small-problem-fixer.md
   • .github/workflows/gh-aw-scheduled-fix.md
   • .github/workflows/gh-aw-release-update.md
2. In .github/workflows/gh-aw-fragments/safe-output-create-pr.md, wire the safe output field under create-pull-request so it honors the new input.
3. Keep backward compatibility: if the input is empty, behavior should remain unchanged (no additional file restrictions).
4. Update user-facing docs/examples to expose the input where users configure PR behavior:
   • gh-agent-workflows/*/README.md for impacted workflows (inputs tables)
   • docs/workflows/detector-fixer-chaining.md and gh-agent-workflows/*/example-chained.yml (show forwarding allowed-files in the fix job)
5. Recompile (make compile) so generated lock files/trigger copies reflect source changes.

Implementation note: please align exact value format with upstream gh-aw allowed-files schema in the referenced docs (https://github.github.com/gh-aw/reference/safe-outputs-pull-requests/#restricting-changes-to-specific-files-with-allowed-files) to avoid parser mismatch.

Related Items

Type	Link	Relevance
Issue	#1701	Request to support optional allowed-files for PR creation
Issue	#831	Prior allowlist-related bug (historical cautionary precedent)
PR	#832	Fix for #831; demonstrates allowlist wiring pitfalls
File	.github/workflows/gh-aw-fragments/safe-output-create-pr.md:125-128	Central create-pull-request safe-output config to extend
File	.github/workflows/gh-aw-create-pr-from-issue.md:25-64	Input surface for chained fixer workflow
Doc	docs/workflows/detector-fixer-chaining.md	Main chain pattern docs needing input forwarding example
External doc	https://github.github.com/gh-aw/reference/safe-outputs-pull-requests/#restricting-changes-to-specific-files-with-allowed-files	Upstream schema/behavior reference for allowed-files

---

What is this? | From workflow: Trigger Issue Triage

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.