GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves merge requests for a specified GitLab group using the GitLab API v4. It allows users to filter and query merge requests based on various criteria such as author, assignee, reviewer, labels, milestone, state, creation and update times, and more. This is useful for project managers, developers, and DevOps teams to monitor and manage merge requests within a group, enabling better collaboration and tracking of code changes.

Use Case Examples

  1. Fetch all merge requests for a group to review pending code changes.
  2. Filter merge requests assigned to a specific user to manage workload.
  3. Retrieve merge requests created after a certain date to track recent activity.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making the API request.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Parameter Schema Defines the parameters for the API request including path and query parameters such as group ID, author, assignee, state, labels, and many others to filter merge requests.
Query Parameters Collection of optional query parameters to filter and customize the merge requests returned by the API, such as author_id, assignee_id, labels, state, created_after, updated_before, and pagination options.
Path Parameters Path parameters required for the API endpoint, specifically the group ID to identify which group's merge requests to retrieve.

Output

JSON

  • merge_requests - Array of merge request objects returned from the GitLab API, each containing details about individual merge requests such as ID, title, state, author, assignee, labels, and timestamps.

Dependencies

  • GitLab API

Troubleshooting

  • Ensure the group ID provided in the path parameters is correct and accessible by the authenticated user.
  • Verify that the authentication credentials (API key/token) are valid and have sufficient permissions to access group merge requests.
  • Check that query parameters are correctly formatted, especially date-time fields in ISO 8601 format.
  • If no merge requests are returned, confirm that the filters applied (e.g., state, author_id) match existing merge requests in the group.

Links

Discussion