> 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-server/2026.2/user-guide/issues/in-devops-platform/gitlab.md).

# Issues reported in GitLab

SonarQube Server 2026.2 reports analysis summary comments in your GitLab merge requests and security issues in GitLab vulnerability report.

## Pull request decoration <a href="#pull-request-decoration" id="pull-request-decoration"></a>

SonarQube Server sets up the report of your quality gate status and analysis metrics directly to your GitLab merge requests. Inline annotations are not supported.

{% hint style="info" %}
Pull request decoration requires that pull request integration be correctly configured for your project. See [Configuring GitLab project binding](/sonarqube-server/2026.2/project-administration/creating-project/gitlab/configure-binding.md).
{% endhint %}

## Vulnerability report <a href="#vulnerability-report" id="vulnerability-report"></a>

When you analyze a project in SonarQube Server, the detected security issues are displayed on the GitLab interface as security vulnerabilities if set up in GitLab CI/CD. See [Configuring GitLab project binding](/sonarqube-server/2026.2/project-administration/creating-project/gitlab/configure-binding.md#reporting-vulnerabilities)for more information. When you change the status of a security issue in the SonarQube Server interface that status change is immediately reflected in the GitLab interface.

{% hint style="warning" %}
If you change the status of a security vulnerability in GitLab, that change is *not* reflected in SonarQube Server.
{% endhint %}

To view the security vulnerabilities:

* Go to the **GitLab** > **Vulnerability** report page.

{% hint style="info" %}
If your issues appear duplicated (it may be the case after the modification of a file), we recommend using the **Activity** > **Still detected** filter.
{% endhint %}

{% 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-server/2026.2/user-guide/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.