> For the complete documentation index, see [llms.txt](https://docs.planetcrust.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.planetcrust.com/human-connections/gitlab/gitlab/query-find-all-merge-requests.md).

# Query: Find All Merge Requests

<p align="center"><a class="button primary" data-icon="circle-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscriptions</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>

<figure><img src="/files/DOMWM02TfCDxLy0uVLRh" alt="" width="375"><figcaption></figcaption></figure>

<p align="center">The Find All Merge Requests query in GitLab retrieves a list of all open or closed merge requests in a project.</p>

{% embed url="<https://www.youtube.com/watch?v=CyuUuaBSZzA>" %}

#### Example User Story

I want to review all pending code changes before the release, so I use the Find All Merge Requests action in GitLab to list and check each one.

#### Fields

| Field Name | Field Type | Required |
| ---------- | ---------- | -------- |
| projectId  | Integer    | Yes      |
| state      | String     | No       |

### Related Connections

[GitLab](/human-connections/gitlab/gitlab.md)

### Related Automations

Example link

### Code (Apache v2.0): Operation

```
{
  "handle": "find-all-merge-requests",
  "state": "inDev",
  "meta": {
    "short": "Find All Merge Requests",
    "description": "Retrieves a list of all merge requests from a GitLab project."
  },
  "input": [
    {
      "name": "projectId",
      "type": "Integer",
      "required": true,
      "meta": {
        "description": "The ID of the GitLab project."
      }
    },
    {
      "name": "state",
      "type": "String",
      "required": false,
      "meta": {
        "description": "Filter merge requests by state (e.g., 'opened', 'closed', 'merged').",
        "default": "opened"
      }
    }
  ],
  "output": [
    {
      "name": "mergeRequests",
      "type": "Array",
      "selector": ["$"],
      "meta": {
        "description": "List of merge requests."
      }
    }
  ],
  "steps": [
    {
      "type": "http",
      "http": {
        "method": "GET",
        "path": "/projects/{{projectId}}/merge_requests",
        "queryParams": {
          "state": "{{state}}"
        }
      }
    }
  ]
}

```

<p align="center"><a class="button primary" data-icon="square-caret-right">Try @Human</a><a class="button primary" data-icon="check">Buy @Human Subscription</a><a class="button primary" data-icon="comments">Join @Human Community</a></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.planetcrust.com/human-connections/gitlab/gitlab/query-find-all-merge-requests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.