GitLab API icon

GitLab API

Gitlab

Actions1062

Merge_requests → getApiV4MergeRequests

AI-generated

Summary

Fetch merge requests from GitLab's API v4 with flexible filtering by various attributes such as author, assignee, reviewer, labels, milestone, state, and more.

Inputs

  • Skip Authentication — Boolean to skip authentication (default: false).
  • baseUrl — The base URL of the GitLab instance (default: https://gitlab.com).
  • Method (required) — HTTP method to use; defaults to GET (used to retrieve merge requests).
  • Query Parameters — Various query parameters to filter merge requests, including author_id, author_username, assignee_id, assignee_username, reviewer_username, labels, milestone, state, order_by, sort, created_before, created_after, updated_before, updated_after, scope (e.g., created_by_me, assigned_to_me, all), source_branch, target_branch, search terms, and others as defined by the GitLab API. Pagination is supported via 'page' and 'per_page'. Many parameters accept special tokens like 'None' or 'Any' to filter accordingly.

Output shape

a list of merge request objects as returned by the GitLab API v4 endpoint /api/v4/merge_requests

The response contains merge requests filtered according to the specified query parameters. Includes pagination control via page and per_page parameters. The structure of each merge request object conforms to GitLab's API definition; if 'with_labels_details' is set to true, label details in the response are more comprehensive. The operation makes an HTTP request to GitLab and returns the API response directly.

Links

Discussion