GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves the issues that are closed by a specific merge request in a GitLab project. It is useful for tracking which issues a merge request resolves, helping in project management and automation workflows. For example, it can be used to automatically update issue statuses or generate reports on merge request impacts.

Use Case Examples

  1. Retrieve closed issues for a merge request to update project tracking.
  2. Automate notifications for issues closed by a merge request.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key or token.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, default is GET.
Query Parameters Optional query parameters for pagination, including page number and items per page.
Path Parameters Required path parameters identifying the project and merge request.

Output

JSON

  • ``
    • id - The ID of the closed issue.
    • title - The title of the closed issue.
    • state - The state of the closed issue (e.g., closed).
    • description - The description of the closed issue.
    • created_at - The creation date of the closed issue.
    • closed_at - The closing date of the issue.

Dependencies

  • GitLab API authentication token or API key

Troubleshooting

  • Ensure the project ID and merge request IID are correct and accessible with the provided authentication.
  • Check that the GitLab base URL is correct if using a self-hosted instance.
  • Verify that the API token has sufficient permissions to read merge requests and issues.
  • Common errors include 404 Not Found if the project or merge request does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion