Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
The "Resolve Discussion" operation in the GitLab Extended node allows users to mark a specific discussion within a merge request as resolved or unresolved. This is useful for managing code review conversations, helping teams track which discussions have been addressed and which still require attention.
Typical scenarios include:
- Automatically resolving discussions after certain automated checks pass.
- Unresolving discussions if further review or changes are needed.
- Integrating with CI/CD pipelines to update discussion statuses based on test results.
For example, a user might use this node to resolve a discussion thread once a related issue has been fixed, signaling to reviewers that no further action is required on that thread.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or providing custom connection details ("Custom"). |
| GitLab Server | Base URL of your GitLab instance (e.g., https://gitlab.com). Used only if "Custom" authentication is selected. |
| Access Token | Personal access token with API permissions. Used only if "Custom" authentication is selected. |
| Project Owner | Namespace or owner of the project. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project Name | Project slug or name. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project ID | Numeric project ID. Takes precedence over owner and name if provided. Used only if "Custom" authentication is selected. |
| Merge Request IID | The internal ID (IID) of the merge request where the discussion exists. Must be a positive number. |
| Discussion ID | The unique identifier of the discussion to resolve or unresolve (e.g., "123abc"). |
| Resolved | Whether to resolve or unresolve the discussion, or leave it unchanged. Options: - Do Not Change - Resolve - Unresolve |
Output
The node outputs JSON data representing the updated discussion object from GitLab's API after the resolve/unresolve action. This typically includes:
- Discussion metadata such as its ID, notes, and resolution status.
- Updated state reflecting whether the discussion is now resolved or unresolved.
No binary data output is involved in this operation.
Dependencies
- Requires access to a GitLab instance via its REST API.
- Needs an API authentication token with sufficient permissions to modify merge request discussions.
- If using "Custom" authentication, the user must provide the GitLab server URL, access token, and project identification details.
- No additional external services are required beyond GitLab.
Troubleshooting
- Invalid or missing Discussion ID: Ensure the Discussion ID corresponds to an existing discussion in the specified merge request.
- Insufficient permissions: The access token must have rights to update merge request discussions; otherwise, the API will reject the request.
- Incorrect Project or Merge Request IID: Verify that the project and merge request identifiers are correct and accessible by the token.
- API errors: Network issues or GitLab API downtime can cause failures; check connectivity and GitLab status.
- "Do Not Change" option selected: If the "Resolved" property is set to "Do Not Change," the node will not alter the discussion's resolution status.