git.pulls.commentComment on a pull request or on a line of it
Request syntax
POST /git/api/repositories/{repoId}/pulls/{prNumber}/comments
{
"body": "string",
"replyToId": "string",
"filePath": "string",
"line": "number",
"side": "enum"
}Path parameters
repoIdRequiredstring
Constraints: uuid
prNumberRequirednumber
Constraints: integer, min 1
Request body
bodyRequiredstring
The comment (Markdown)
Constraints: 1-20000 chars
replyToIdOptionalstring
The comment this one answers, in its thread
Constraints: uuid
filePathOptionalstring
For a comment on a line: the changed file; give line and side with it
Constraints: 1-1000 chars
lineOptionalnumber
For a comment on a line: the line number in the file on `side`
Constraints: integer, min 1
sideOptionalenum
For a comment on a line: `new` is the head version, `old` the version before
One of:
old,new
Response
201 with the comment; an inline one carries the head commit its line refers to. 422 when the line is not in the diff.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
The comment idprIdAlwaysstring
The pull requestorgIdAlwaysstring
The organizationauthorIamUserIdAlwaysstring
Who wrote itbodyAlwaysstring
The comment (Markdown)filePathAlwaysstring, may be null
For an inline comment, the file; null otherwiselineAlwaysnumber, may be null
For an inline comment, the line; null otherwisesideAlwaysone of old, new, may be null
For an inline comment, the old or new side of the diff; null otherwisecommitOidAlwaysstring, may be null
For an inline comment, the head commit its line refers toresolvedAtAlwaysstring, may be null
When the thread was resolved (on a thread's first comment); null when openresolvedByIamUserIdAlwaysstring, may be null
Who resolved the thread; null when openreplyToIdAlwaysstring, may be null
The comment this replies to; null for a thread rootcreatedAtAlwaysstring
When it was writtenupdatedAtAlwaysstring
When it last changed
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:ReviewPullRequest 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 comment repoId prNumber --body examplecurl -X POST "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/pulls/prNumber/comments" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"body":"example"}'Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_pulls_comment.