Submission requirements
Problem summary
create-pull-request supports reviewers only through static workflow frontmatter:
safe-outputs:
create-pull-request:
reviewers:
- user@example.comThe model-facing CreatePrParams accepts title, description, repository, and labels, but not reviewers. This prevents workflows from selecting reviewers dynamically—for example, adding the assignee of the issue that triggered an autofix workflow.
Reproduction details
- Create an issue-triggered workflow that opens an Azure DevOps PR.
- Provide the authoritative issue assignee to the model.
- Ask the model to add that assignee as a reviewer.
- The model cannot include reviewers in its
create-pull-request call.
update-pr supports dynamic reviewers, but requires a numeric PR ID that does not exist until safe-output execution.
This leaves custom post-processing scripts or hardcoded reviewers as the only options.
Expected: the model can propose reviewers as part of create-pull-request, subject to safe-output policy and threat detection.
Proposed next step
Add an optional reviewers field to CreatePrParams.
During safe-output execution, merge and deduplicate model-supplied reviewers with statically configured reviewers, then use the existing reviewer identity resolution and PR reviewer APIs.
Consider requiring explicit operator opt-in, such as allow-agent-reviewers: true or an allowed-reviewers policy. Update the tool schema, documentation, and executor tests accordingly.
Posted by Copilot CLI assistant.
Submission requirements
.github/agents/ado-aw.agent.md.githubnext/ado-aw.Problem summary
create-pull-requestsupports reviewers only through static workflow frontmatter:The model-facing
CreatePrParamsaccepts title, description, repository, and labels, but not reviewers. This prevents workflows from selecting reviewers dynamically—for example, adding the assignee of the issue that triggered an autofix workflow.Reproduction details
create-pull-requestcall.update-prsupports dynamic reviewers, but requires a numeric PR ID that does not exist until safe-output execution.This leaves custom post-processing scripts or hardcoded reviewers as the only options.
Expected: the model can propose reviewers as part of
create-pull-request, subject to safe-output policy and threat detection.Proposed next step
Add an optional
reviewersfield toCreatePrParams.During safe-output execution, merge and deduplicate model-supplied reviewers with statically configured reviewers, then use the existing reviewer identity resolution and PR reviewer APIs.
Consider requiring explicit operator opt-in, such as
allow-agent-reviewers: trueor anallowed-reviewerspolicy. Update the tool schema, documentation, and executor tests accordingly.Posted by Copilot CLI assistant.