GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves merge requests associated with a specific deployment in a GitLab project. It is useful for users who want to track or analyze merge requests related to a particular deployment, such as reviewing code changes that were deployed or monitoring deployment-related merge requests in a CI/CD pipeline.

Use Case Examples

  1. Fetch all merge requests for a deployment in a project to review changes before production release.
  2. Filter merge requests by author, state, or labels to analyze deployment impact.
  3. Paginate through merge requests related to a deployment for detailed reporting.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated access.
Authentication Type of authentication used, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Parameter Schema Defines the path and query parameters for the API call, including project ID, deployment ID, pagination, filters like author, assignee, state, labels, dates, and other merge request attributes.
Query Parameters Collection of optional query parameters to filter and customize the merge requests returned, such as page, per_page, author_id, state, labels, created_after, and more.
Path Parameters Path parameters specifying the project ID and deployment ID to identify the deployment for which merge requests are fetched.

Output

JSON

  • merge_requests - Array of merge request objects related to the specified deployment, including details like title, state, author, labels, and timestamps.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID and deployment ID are correct and accessible by the authenticated user to avoid 404 errors.
  • Check that the authentication credentials are valid and have sufficient permissions to access the project and deployment data.
  • Verify that query parameters are correctly formatted, especially date-time fields in ISO 8601 format, to prevent request errors.
  • If no merge requests are returned, confirm that there are merge requests associated with the specified deployment and that filters are not overly restrictive.

Links

Discussion