git.issues.commentComment on an issue
POST /git/api/repositories/{repoId}/issues/{number}/commentsIAM git:CommentOnIssueChanges state
Request syntax
POST /git/api/repositories/{repoId}/issues/{number}/comments
{
"body": "string"
}Path parameters
repoIdRequiredstring
Constraints: uuid
numberRequirednumber
Constraints: integer, min 1
Request body
bodyRequiredstring
The comment (Markdown)
Constraints: 1-65536 chars
Response
201 with the comment: id, issueId, authorIamUserId, body and createdAt.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
The comment idorgIdAlwaysstring
The organization it belongs toissueIdAlwaysstring
The issue it is onauthorIamUserIdAlwaysstring, may be null
The IAM user who wrote it; null once that user is deletedbodyAlwaysstring
The comment (Markdown)createdAtAlwaysstring
When it was written (ISO 8601)
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:CommentOnIssue 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 issues comment repoId number --body examplecurl -X POST "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/issues/number/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_issues_comment.