Copilot cloud agent opens a draft pull request. Who can merge it?
Why B is the answer
A person, because the agent cannot approve or merge
The agent cannot mark its pull request ready, approve it or merge it. A human must do that.
In detail
- The agent cannot approve or merge.
- A person has to do it.
- This keeps a person in the path to production.
Use case
An illustrative scenario, not a real incident.
A draft pull request from the cloud agent passes its checks. It still waits, because the agent cannot approve or merge, and a person must.
See it in different ways
sequenceDiagram participant D as Developer participant A as Cloud agent participant G as Repository participant R as Reviewer D->>A: Assign a task A->>G: Push to a copilot branch A->>G: Open a draft pull request R->>G: Review, then approve and merge
sequenceDiagram participant D as Developer participant A as Cloud agent participant P as Another reviewer D->>A: Requests a pull request A->>P: Draft pull request P->>P: Approve and run workflows P->>A: Review and merge
sequenceDiagram participant P0 as Cloud agent participant P1 as Pull request participant P2 as Reviewer P0->>P1: Opens a draft P2-->>P1: Reviews and merges
Key point: Agents cannot approve or merge.
Why the other options are wrong
- A. The agent, if the repository owner has allowed it
- An owner setting does not give it that right.
- C. Anyone at all, including users with no repository access
- Merging needs repository access.
- D. The agent, once all of its checks have passed
- Passing checks does not let it merge.