GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves resource milestone events associated with a specific merge request in a GitLab project. It is useful for tracking milestone changes or events related to merge requests within a project. For example, it can be used to monitor when milestones are added, updated, or removed from a merge request, aiding project management and automation workflows.

Use Case Examples

  1. Fetch milestone events for a merge request to update project status dashboards.
  2. Automate notifications when a milestone event occurs on a merge request.

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.
Parameter Schema Defines required and optional parameters for the API call, including project ID, eventable ID, page number, and items per page.
Query Parameters Optional query parameters for pagination such as page number and items per page.
Path Parameters Path parameters including the project ID and eventable ID to specify the resource.

Output

JSON

  • ``
    • id - Unique identifier of the milestone event.
    • action - Action performed on the milestone event.
    • created_at - Timestamp when the milestone event was created.
    • milestone - Details of the milestone associated with the event.
    • user - User who triggered the milestone event.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID and eventable ID are correctly specified and URL-encoded if necessary.
  • Verify that the GitLab API key credential is valid and has sufficient permissions to access the project and merge request data.
  • Check the base URL if using a self-hosted GitLab instance to ensure it is correct.
  • Pagination parameters (page and per_page) should be set appropriately to avoid missing data or excessive data retrieval.

Links

Discussion