GitLab API

GitlabTool
Join our community

Actions1000

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 auditing deployment history. For example, a DevOps engineer might use this to fetch all merge requests linked to a deployment to verify what changes were included.

Use Case Examples

  1. Fetch merge requests for deployment ID 123 in project 'my-project' to review changes before production release.
  2. Retrieve merge requests assigned to a specific user for a deployment to track code review progress.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request (GET, POST, PUT, DELETE, HEAD, PATCH).
Query Parameters Collection of optional query parameters to filter and customize the merge requests returned, such as page, per_page, author_id, state, labels, milestone, and many others.
Path Parameters Parameters required in the URL path, specifically the project ID or URL-encoded path and the deployment ID to identify the deployment.

Output

JSON

  • merge_requests - Array of merge request objects related to the specified deployment.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID and deployment ID are correctly specified and exist in the GitLab instance.
  • Verify that the authentication token has sufficient permissions to access deployment and merge request data.
  • Check that optional query parameters are correctly formatted and valid according to GitLab API specifications.
  • Common error messages may include 404 Not Found if the deployment or project does not exist, or 401 Unauthorized if authentication fails.

Links

Discussion