git.labels.set-pull-request-assignees

Replace a pull request’s assignees

PUT /git/api/repositories/{repoId}/pulls/{prNumber}/assigneesIAM git:UpdateIssueChanges state

Members of the organization, as on an issue; each change is a timeline entry.

Request syntax

PUT /git/api/repositories/{repoId}/pulls/{prNumber}/assignees
{
  "assigneeIamUserIds": "array of string"
}

Path parameters

  • repoIdRequired

    string

    Constraints: uuid

  • prNumberRequired

    number

    Constraints: integer, min 1

Request body

  • assigneeIamUserIdsRequired

    array of string

    Replaces the assignees

    Constraints: uuid

Response

200 with `assigneeIamUserIds`, the assignees now. 422 names an IAM user that does not exist.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Fields of data

  • assigneeIamUserIdsAlways

    array of string

    The IAM users the pull request is assigned to now

Checked against the handlers: every route test validates their answers against this schema.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow git:UpdateIssue on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud git labels set-pull-request-assignees repoId prNumber --assignee-iam-user-ids '["example"]'

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_labels_set-pull-request-assignees.