# Configuring GitLab project binding

Once your GitLab group has been imported to SonarQube Cloud, you can create your SonarQube Cloud project by importing your GitLab repository. The created SonarQube Cloud project is bound to its GitLab repository. To bind an unbound project, see [#binding-an-unbound-project-to-a-repository](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/changing-binding#binding-an-unbound-project-to-a-repository "mention").

## Setting up pull request integration

For a bound project, the quality gate status and analysis metrics are reported to your pull requests in GitLab provided:

* Your build script is configured to build on pull request creation and push.
* If you don't use an integrated CI tool, you must set up the pull request parameters manually, see [#pull-request-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/analysis-parameters#pull-request-analysis "mention") for more details.
* See [#prerequisites-for-ci-based-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/pull-request-analysis#prerequisites-for-ci-based-analysis "mention") for additional information.

<details>

<summary>Preventing the pull request merge if the quality gate fails</summary>

In GitLab, you can block merge requests if it is failing the quality gate. To do this:

1. In your GitLab repository, go to *Your project* **> Settings > Merge requests.**
2. In the **Merge Checks** section, select **Pipelines must succeed**. More information about GitLab’s External status checks can be found in the [GitLab Documentation](https://docs.gitlab.com/ee/user/project/merge_requests/status_checks.html#block-merges-of-merge-requests-unless-all-status-checks-have-passed).
3. Set up the pipeline to fail. It depends on your CI tool:
   * GitLab CI: see [#failing-the-pipeline-job-when-the-sonarqube-cloud-quality-gate-fails](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/ci-based-analysis/gitlab-ci#failing-the-pipeline-job-when-the-sonarqube-cloud-quality-gate-fails "mention")
   * GitHub Actions: see [#failing-workflow-on-quality-gate-failure](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/ci-based-analysis/github-actions-for-sonarcloud#failing-workflow-on-quality-gate-failure "mention")
   * Bitbucket Pipelines: see [#failing-the-pipeline-job-when-the-quality-gate-fails](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/ci-based-analysis/bitbucket-pipelines-for-sonarcloud#failing-the-pipeline-job-when-the-quality-gate-fails "mention")

{% hint style="info" %}
The blocking of pull requests on quality gate failure is not supported for projects on a monorepo.
{% endhint %}

</details>

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

* [gitlab](https://docs.sonarsource.com/sonarqube-cloud/getting-started/gitlab "mention")
* [importing-gitlab-group](https://docs.sonarsource.com/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-gitlab-group "mention")
* [setting-up-project](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/administering-your-projects/setting-up-project "mention")
* [gitlab-ci](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/ci-based-analysis/gitlab-ci "mention")
* [setting-permissions](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/administering-your-projects/setting-permissions "mention")
* [changing-binding](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/administering-your-projects/changing-binding "mention")
* [customizing-info-page](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/administering-your-projects/customizing-info-page "mention")
* [deleting-project](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/administering-your-projects/deleting-project "mention")