Skip to content

Issue #20664 still unresolved in v0.58.0: target-repo remains unsupported in safe-outputs.submit-pull-request-review #20781

@alexsiilvaa

Description

@alexsiilvaa

A issue #20664 appears to still be unresolved in the published version v0.58.0.
After updating gh aw, the field target-repo is still rejected during workflow compilation.

Environment

  • OS: Windows
  • gh aw version: v0.58.0

Steps to reproduce

  • Update gh aw to v0.58.0.
  • Use a workflow with safe-outputs.submit-pull-request-review containing target-repo.
  • Run: gh aw compile

Actual behavior
Compilation fails with an unknown property error for target-repo:

.github\workflows\test.md:40:5: error: at '/safe-outputs/submit-pull-request-review' (line 40, column 5): Unknown property: target-repo. Valid fields are: footer, github-token, max, target. 'target-repo' belongs under 'tools/repo-memory', 'safe-outputs/create-code-scanning-alert' or 'safe-outputs/hide-comment'

Expected behavior
target-repo should be supported for submit-pull-request-review (as expected from issue #20664 being resolved), and compilation should succeed in v0.58.0.

Impact
This blocks workflows that need to target a repository explicitly when submitting pull request reviews, even after upgrading to the version that should include the fix.

Additional note
If the expected behavior changed intentionally, please document the migration path and the supported alternative for this use case.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions