> 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/2025.5/project-administration/changing-project-binding.md).

# Changing your project binding

In SonarQube Server 2025.5, you can bind an unbound project and you can change the binding of a bound project.

You must be an administrator of your project.

## Unbinding or changing the binding of a bound project

1. Retrieve your project. For more information, see [Retrieving projects](/sonarqube-server/2025.5/user-guide/viewing-projects/retrieving-projects.md).
2. Go to **Project Settings** > **General Settings** > **DevOps Platform Integration**.
3. In the bottom of the page, select **Reset**. The project is unbound.
4. To bind the project to another repository, see [#binding-an-unbound-project](#binding-an-unbound-project "mention") below.

## **Binding an unbound project**

If you created your project manually and want to bind it to its DevOps platform repository to benefit the features of a bound project, proceed as follows:

1. Retrieve your project in SonarQube Server. For more information, see [Retrieving projects](/sonarqube-server/2025.5/user-guide/viewing-projects/retrieving-projects.md)..
2. In front of the project name, select **Bind project**. The DevOps Platform Integration page opens.

<figure><img src="broken://spaces/KXW79zfYFiA8incTvwZK/files/RRLa1nm2q05TNwhbTRBJ" alt="Select bind project from the project overview page."><figcaption></figcaption></figure>

3. In **Configuration name**, enter the Configuration record used to manage your DevOps platform integration at the global level. Ask your system administrator.
4. This step depends on your DevOps platform:
   * GitHub: In **Repository name**, enter the name of the GitHub repository you want to bind.\
     You can enable the [analysis summary under the GitHub Conversation tab](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/in-devops-platform/github#pull-request-decoration).
   * Bitbucket Cloud: In **Repository slug**, enter the URL of the Bitbucket Cloud repository you want to bind.
   * GitLab: In **Project ID**, enter the unique identifier of your GitLab project you want to bind.
   * Azure DevOps:
     * In **Project name**, enter the name of the Azure DevOps project containing your repository.
     * In **Repository name**, enter the name of the Azure DevOps repository you want to bind.
     * By default, [pull request annotations](https://docs.sonarsource.com/sonarqube-server/user-guide/issues/in-devops-platform/azure-devops#pull-request-decoration) are enabled. You can disable them.
5. Select **Save**. The new binding is saved.

<figure><img src="broken://spaces/KXW79zfYFiA8incTvwZK/files/eFOsMCh4J7yfLbQsHq8f" alt="Once you have saved your project binding configuration, select the Check configuration button."><figcaption></figcaption></figure>

6. Select **Check configuration**. SonarQube Server checks if the entered DevOps platform repository exists and you have access to it.

{% hint style="info" %}
The project binding (incl. the configuration check) is logged in the [audit logs](/sonarqube-server/2025.5/server-update-and-maintenance/monitoring/audit-logs.md).
{% 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/2025.5/project-administration/changing-project-binding.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.