# Setting up GitHub integration for your project

## Setting up pull request integration <a href="#pull-request-integration" id="pull-request-integration"></a>

For bound projects (projects created by importing the GitHub repository), pull request decoration is supported in GitHub provided the pull request analysis has been properly set up in your project. See [Setting up the pull request analysis](/sonarqube-server/2025.6/analyzing-source-code/pull-request-analysis/setting-up-the-pull-request-analysis.md).

You can bind an existing and manually created project to its GitHub repository provided the global integration of SonarQube Server with GitHub has been properly set up. To do so, see [Changing your project binding](/sonarqube-server/2025.6/project-administration/maintaining-project/changing-project-binding.md).

## Disabling the analysis summary in GitHub Conversation tab <a href="#disable-summary-in-conversation-tab" id="disable-summary-in-conversation-tab"></a>

By default, SonarQube Server shows the analysis summary in the Conversation and Checks tab of your GitHub pull requests.

To disable the summary in the Conversation tab:

1. Retrieve your SonarQube Server project. For more information, see [Retrieving projects](/sonarqube-server/2025.6/user-guide/viewing-projects/retrieving-projects.md).
2. Go to **Project Settings** > **General Settings** > **DevOps Platform Integration.**
3. Unselect **Enable analysis summary under the GitHub Conversation tab**.

## Preventing pull request merges when the quality gate fails <a href="#preventing-pull-request-merges" id="preventing-pull-request-merges"></a>

In GitHub, you can block pull requests from being merged if it is failing the quality gate. To do this:

1. In GitHub, go to your repository **Settings** > **Branches** > **Branch protection rules** and select either the **Add rule** or **Edit** button if you already have a rule on the branch you wish to protect.
2. Complete the **Branch protection rule** form:
   * Define the **Branch name pattern** (the name of the branch you wish to protect)
   * Select **Require status checks to pass before merging** to open supplementary form fields.
   * In the **Search for status checks in the last week** for this repository field, select **Require branches to be up to date before merging**, then find `SonarQube Code Analysis` and add it to the list of required checks.

## Related pages

* [Issues reported in GitHub](/sonarqube-server/2025.6/user-guide/issues/in-devops-platform/github.md)
* [Setting up the report of security alerts](/sonarqube-server/2025.6/devops-platform-integration/github-integration/setting-up-at-global-level/report-security-alerts.md)


---

# Agent Instructions: 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:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.6/devops-platform-integration/github-integration/setting-up-at-project-level.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.