GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation updates a specific merge request in a GitLab project using the GitLab API. It is useful for scenarios where you need to modify details of an existing merge request, such as changing its title, description, or other attributes. For example, a developer or DevOps engineer might use this node to programmatically update merge requests as part of an automated workflow or CI/CD pipeline.

Use Case Examples

  1. Updating the title or description of a merge request in a GitLab project.
  2. Changing the target branch or other merge request settings via automation.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, typically a GitLab API key credential.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to GET but can be set to PUT for this operation.
Path Parameters Parameters required in the URL path to identify the project and merge request to update.

Output

JSON

  • id - The ID or URL-encoded path of the project.
  • merge_request_iid - The internal ID of the merge request.
  • updated_fields - Fields updated in the merge request as per the request body.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID and merge request IID are correctly specified; incorrect values will cause the API call to fail.
  • Verify that the authentication credentials are valid and have sufficient permissions to update merge requests.
  • Check that the request body schema matches the expected structure for updating a merge request in GitLab API.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid project or merge request ID), and 400 Bad Request (invalid request body).

Links

Discussion