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 changes merged during a deployment or auditing deployment history.

Use Case Examples

1. Fetch merge requests for deployment ID 123 in project 'my-project' to review changes included in that deployment.
2. List all merge requests assigned to a specific user that were part of a deployment to monitor team contributions.

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, including the project ID or URL-encoded path and the deployment ID.

Output

JSON

• id - The unique identifier of the merge request.
• iid - Internal ID of the merge request within the project.
• project_id - ID of the project the merge request belongs to.
• title - Title of the merge request.
• description - Description of the merge request.
• state - Current state of the merge request (e.g., opened, closed, merged).
• created_at - Timestamp when the merge request was created.
• updated_at - Timestamp when the merge request was last updated.
• merged_at - Timestamp when the merge request was merged, if applicable.
• author - Information about the user who created the merge request.
• assignee - Information about the user assigned to the merge request.
• labels - Labels associated with the merge request.
• milestone - Milestone associated with the merge request.
• merge_status - Current merge status of the merge request.

Dependencies

• GitLab API authentication token or credentials

Troubleshooting

• Ensure the project ID and deployment ID path parameters are correctly provided and URL-encoded if necessary.
• Verify that the authentication credentials (API token) are valid and have sufficient permissions to access the project's deployment and merge requests.
• Check that the query parameters are correctly formatted and valid according to GitLab API specifications.
• Common error messages may include 404 Not Found if the project or deployment does not exist, or 401 Unauthorized if authentication fails.

Links

• GitLab API - Get deployment merge requests - Official GitLab API documentation for retrieving merge requests associated with a deployment.