Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
This node operation updates an existing note on a GitLab merge request discussion. It allows users to modify the content of a specific note identified by its note ID within a particular discussion thread on a merge request. This is useful for correcting, clarifying, or adding additional information to comments already made in code review discussions.
Typical use cases include:
- Amending feedback or comments on a merge request after initial posting.
- Fixing typos or errors in notes without creating new ones.
- Updating notes to reflect changes in the code or discussion context.
For example, if a reviewer wants to update their comment on a merge request discussion to add more details or correct a mistake, this operation enables that directly via the node.
Properties
| Name | Meaning |
|---|---|
| Merge Request IID | The internal ID (IID) of the merge request where the note exists, e.g., 7. |
| Discussion ID | The identifier of the discussion thread containing the note to update, e.g., 123abc. |
| Note ID | The unique numeric ID of the existing note to update, e.g., 50. |
| Note Body | The updated text content of the note, e.g., "Looks good to me". |
Output
The node outputs JSON data representing the updated note object returned from the GitLab API. This typically includes fields such as the note's ID, body text, author information, timestamps, and any metadata related to the note within the merge request discussion.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential with access to the target GitLab project.
- The node uses the GitLab Extended API integration configured with project identification (either by project ID or owner/name).
- Proper permissions are needed to update notes on merge requests in the GitLab repository.
Troubleshooting
- Invalid Discussion ID or Note ID: If the provided discussion or note IDs do not exist or are incorrect, the API will return an error indicating the resource was not found. Verify these IDs carefully.
- Insufficient Permissions: Errors related to authorization may occur if the API token lacks rights to edit notes. Ensure the token has appropriate scopes.
- Empty Note Body: Providing an empty string for the note body might cause validation errors. Always supply meaningful content.
- Malformed Input: Non-numeric values for IDs or missing required parameters will cause errors. Double-check input types and required fields.