> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/issues/in-devops-platform/gitlab.md).

# Issues reported in GitLab

SonarQube Cloud reports analysis summary comments in your GitLab merge requests.

{% hint style="info" %}
SonarQube Cloud, unlike SonarQube Server, doesn't support the report of vulnerabilities in GitLab.
{% endhint %}

## Merge request decoration

SonarQube Cloud leaves analysis summary comments on your GitLab merge requests. Inline comments are not supported.

{% hint style="info" %}
Merge request decoration is only supported with a bound project and requires that pull request integration be correctly configured for your project. See [Configuring GitLab project binding](/sonarqube-cloud/managing-your-projects/administering-your-projects/devops-platform-integration/gitlab.md) for more details.
{% endhint %}

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Configuring GitLab project binding](/sonarqube-cloud/managing-your-projects/administering-your-projects/devops-platform-integration/gitlab.md)

{% hint style="info" %}
For AI-powered review comments directly in merge requests, see [Gitar](https://docs.gitar.ai/features/code-review), a separate Sonar product.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/issues/in-devops-platform/gitlab.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.