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 → Resolve Discussion
AI-generatedSummary
Set the resolved state of a specific discussion within a merge request in a GitLab project to resolve or unresolve it.
Inputs
- Authentication — Choose between using saved credentials or custom credentials (default is saved credentials).
- GitLab Server — Base URL of the GitLab instance, required only if using custom authentication (default: https://gitlab.com).
- Access Token — Personal access token with API permissions, required only if using custom authentication.
- Project Locator — Method to identify the project, either by ID or by path (default: id).
- Project ID — Numeric project ID, used if Project Locator is set to 'ID'.
- Project Owner — Namespace or owner of the project, used if Project Locator is set to 'Path'.
- Project Name — Project slug or name, used if Project Locator is set to 'Path'.
- Merge Request IID (required) — The internal ID of the merge request (positive integer).
- Discussion ID (required) — Unique identifier of the discussion to modify.
- Resolved — Choose to resolve, unresolve, or leave the resolved state unchanged (default is no change).
Output shape
a single record representing the updated discussion object
The operation sends a PUT request to update the 'resolved' boolean of the specified discussion. If 'Do Not Change' is selected for 'Resolved', no update is sent. Returns the updated discussion data as JSON.
Examples
Example 1: Resolve a discussion
Set 'Resolved' to 'Resolve' and specify the 'Merge Request IID' and 'Discussion ID' to mark it as resolved.
Example 2: Unresolve a discussion
Set 'Resolved' to 'Unresolve' and specify the 'Merge Request IID' and 'Discussion ID' to mark it as unresolved.