In the NotesAPI, when calling createMergeRequestNote (https://docs.gitlab.com/api/notes/#create-new-merge-request-note), if you use entirely Quick Actions, no note is created. This also means the response body doesn't match the Note class. Instead, it has the following fields:
- commands_changes: A map showing all the changed fields in the MR
- summary: A string that is a summary of all the changes made, and errors if there were any
For example:
curl -vvv --request POST \
--header "PRIVATE-TOKEN: glpat-<REDACTED>" \
--header "Content-Type: application/json" \
--data '{"body": "/draft\n/assign_reviewer @GitLabDuo\n/label ~\"my-test\""}' \
"https://gitlab.com/api/v4/projects/9372/merge_requests/22/notes"{
"commands_changes": {
"add_label_ids": [
432
],
"wip_event": "draft"
},
"summary": [
"No change to this merge request's draft status. Your account doesn't have GitLab Duo access. Please contact your system administrator for access. Added ~\"my-test\" label."
]
}
In the
NotesAPI, when callingcreateMergeRequestNote(https://docs.gitlab.com/api/notes/#create-new-merge-request-note), if you use entirely Quick Actions, no note is created. This also means the response body doesn't match theNoteclass. Instead, it has the following fields:For example:
{ "commands_changes": { "add_label_ids": [ 432 ], "wip_event": "draft" }, "summary": [ "No change to this merge request's draft status. Your account doesn't have GitLab Duo access. Please contact your system administrator for access. Added ~\"my-test\" label." ] }