git.pulls.apply-suggestion

Commit a review comment's suggested change to the pull request's branch

POST /git/api/repositories/{repoId}/pulls/{prNumber}/comments/{commentId}/apply-suggestionIAM git:PushRepositoryChanges stateDestructive

The comment must be on a line of the new side and carry a ```suggestion block; it replaces that line (empty deletes it). Refused once the branch has moved since the comment (409), and subject to branch protection like a push. Resolves the thread.

Request syntax

POST /git/api/repositories/{repoId}/pulls/{prNumber}/comments/{commentId}/apply-suggestion

Path parameters

  • repoIdRequired

    string

    Constraints: uuid

  • prNumberRequired

    number

    Constraints: integer, min 1

  • commentIdRequired

    string

    Constraints: uuid

Response

200 with `commitOid`, the new commit on the pull request's branch.

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

Fields of data

  • commitOidAlways

    string

    The new commit on the pull request's branch

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:PushRepository 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 pulls apply-suggestion repoId prNumber commentId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_pulls_apply-suggestion.