> 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/10.8/analyzing-source-code/branch-analysis/introduction.md).

# Introduction

In SonarQube Server 10.8, the branch analysis allows you to trigger an analysis on a push to any long-living branch or to short-lived branches without involving pull requests.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.8 documentation. For a list of all 10.8 pages, see the [SonarQube Server 10.8 page index](https://312504542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiJj3TXBdWssTGGg8qK5I%2Fuploads%2FmeJ1nVNGPezOurNrTy4A%2Fsonarqube-server-10.8-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.8 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

*Branch analysis is available starting in* [*Developer Edition*](https://www.sonarsource.com/plans-and-pricing/developer/)*.*

The branch analysis allows you to trigger an analysis on a push to any specified branch (not just the main branch) without involving pull requests. This capability can be useful in the following situations:

* If your project has long-living branches other than the main branch that you want to analyze. One use case is having branches for older versions of your software that you still periodically update with critical fixes. Another is having separate branches for development and production in your project.
* If you use short-lived branches (for example, "feature" branches) to introduce changes to your main branch but do not use them with a pull request mechanism in a supported CI.

You can limit the branch analysis to relevant branches only.

## Improving code quality <a href="#clean-as-you-code" id="clean-as-you-code"></a>

The quality gate of your project applies to your branch (you cannot define a quality gate at the branch level). It lets you know if your branch is ready to be merged.

[About new code](/sonarqube-server/10.8/core-concepts/clean-as-you-code/about-new-code.md) at the branch level.

## Incremental branch analysis <a href="#incremental-analysis" id="incremental-analysis"></a>

Some analyzers use the [Introduction](/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/introduction.md) to shorten the branch analysis. This way, they analyze only the code sections that are affected by the changes in the branch compared to the previous analysis.

## Issue synchronization <a href="#issue-synchronization" id="issue-synchronization"></a>

SonarQube Server synchronizes issue attributes (status, assignee, change log, comments) between branches when a branch is created or (under particular conditions) merged. For more information, see the corresponding section on the [Issue management solution](/sonarqube-server/10.8/user-guide/issues/solution-overview.md) page.

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

* [Setting up the branch analysis](/sonarqube-server/10.8/analyzing-source-code/branch-analysis/setting-up-the-branch-analysis.md)
* [Maintaining project branches](/sonarqube-server/10.8/project-administration/maintaining-the-branches-of-your-project.md).
* [Introduction](/sonarqube-server/10.8/analyzing-source-code/incremental-analysis/introduction.md)


---

# 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/10.8/analyzing-source-code/branch-analysis/introduction.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.