Actions71
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Merge Request → Update Discussion
AI-generatedSummary
Update the resolved state of a specific discussion in a GitLab merge request.
Inputs
- Authentication — Choose between using saved credentials or custom GitLab API credentials.
- GitLab Server — Base URL of the GitLab instance, required if using custom authentication.
- Access Token — Personal access token with API permissions, required if using custom authentication.
- Project Locator — Method to identify the project: by numeric ID or by path (project owner and name). Defaults to ID.
- Project ID — Numeric ID of the project when identifying by ID.
- Project Owner — Namespace or owner of the project when identifying by path.
- Project Name — Project slug or name when identifying by path.
- Merge Request IID (required) — Internal ID of the merge request containing the discussion to update.
- Discussion ID (required) — ID of the discussion to update.
- Resolved — Set discussion resolved state: resolve, unresolve, or do not change (default).
Output shape
a single updated discussion object
Returns the updated discussion data from GitLab API after setting the resolved state. Requires valid project and merge request identification.
Examples
Example 1: Mark a merge request discussion as resolved
Provide project identification (ID or path), merge request IID, discussion ID, and set Resolved to 'Resolve'. The node updates the discussion's resolved state accordingly.