GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves a specific resource milestone event associated with a merge request in a GitLab project. It is useful for users who want to fetch detailed information about milestone events tied to merge requests, such as tracking progress or status changes within a project milestone context. For example, a project manager might use this to monitor milestone events for a particular merge request to ensure timely delivery.

Use Case Examples

  1. Fetch details of a milestone event for a merge request in a GitLab project to track project progress.
  2. Retrieve milestone event information to audit changes or updates related to project milestones.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, defaulting to GitLab API key.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Path Parameters Parameters required in the request path to identify the project, merge request, and milestone event.

Output

JSON

  • id - The unique identifier of the resource milestone event.
  • title - The title or name of the milestone event.
  • created_at - Timestamp when the milestone event was created.
  • updated_at - Timestamp when the milestone event was last updated.
  • project_id - The ID of the project associated with the milestone event.
  • merge_request_id - The ID of the merge request associated with the milestone event.
  • milestone_id - The ID of the milestone related to the event.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID, merge request ID (eventable_id), and milestone event ID (event_id) are correctly provided; incorrect IDs will result in errors or no data returned.
  • Authentication errors may occur if the GitLab API key is missing, invalid, or lacks necessary permissions; verify the API key and its scopes.
  • Network or base URL misconfiguration can cause connection failures; confirm the baseUrl is correct and accessible.
  • If the milestone event does not exist or is not accessible due to permissions, the node will return an error or empty response.

Links

Discussion