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
Link to the gh-aw PR: github/gh-aw#47400 — fix: downgrade REQUEST_CHANGES→COMMENT on self-authored PRs in safe-outputs PR review
When the reviewing identity matches the PR author, GitHub rejects REQUEST_CHANGES with 422 "Can not request changes on your own pull request". The fix ensures reviewer workflows fall back to COMMENT in this case. Previously the fallback was bypassed when another 422 ("Line could not be resolved") occurred first. There is no regression test for this scenario.
Dispatch a review against a pull request authored by the same bot identity running the workflow. Ask the agent to request changes. The test passes if the review is successfully submitted (as a COMMENT) rather than failing with a 422 error.
New fixtures or secrets needed
Requires a PR in githubnext/gh-aw-test authored by the same bot/app identity that submits the review. This may require a dedicated fixture PR or a test-setup step that creates such a PR.
Notes
The existing test-copilot-submit-pull-request-review.md and test-copilot-submit-pull-request-review-locked.md both use PRs authored by a different identity. A self-authored PR fixture is the key missing element.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpg
To allow these domains, add them to the network.allowed list in your workflow frontmatter:
Motivation
Link to the gh-aw PR: github/gh-aw#47400 — fix: downgrade REQUEST_CHANGES→COMMENT on self-authored PRs in safe-outputs PR review
When the reviewing identity matches the PR author, GitHub rejects
REQUEST_CHANGESwith 422 "Can not request changes on your own pull request". The fix ensures reviewer workflows fall back toCOMMENTin this case. Previously the fallback was bypassed when another 422 ("Line could not be resolved") occurred first. There is no regression test for this scenario.Proposed test
test-copilot-submit-pull-request-review-self-authored-fallback.mdworkflow_dispatchsubmit-pull-request-reviewMinimal test prompt sketch
Dispatch a review against a pull request authored by the same bot identity running the workflow. Ask the agent to request changes. The test passes if the review is successfully submitted (as a COMMENT) rather than failing with a 422 error.
New fixtures or secrets needed
Requires a PR in
githubnext/gh-aw-testauthored by the same bot/app identity that submits the review. This may require a dedicated fixture PR or a test-setup step that creates such a PR.Notes
The existing
test-copilot-submit-pull-request-review.mdandtest-copilot-submit-pull-request-review-locked.mdboth use PRs authored by a different identity. A self-authored PR fixture is the key missing element.Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.