# Checked-out code

The SonarScanners run on code that is checked out from the repository (for more information, see [#ci-pipeline](https://docs.sonarsource.com/sonarqube-server/2026.1/discovering/analysis-overview/process-steps#ci-pipeline "mention")). During the checkout of a working copy (clone) of the code from the project repository, we recommend using the full depth. Indeed, the so-retrieved SCM data enables various features such as:

* New Code detection:
  * On pull requests, not just the last commit but all the commits that are not on the target branch are considered. This requires a history long enough to find the common commit.
  * On long-living branches, the New Code definition can be set in different ways but a longer history is always better.
* Blame information display and automatic issue assignment based on the blame information.
* Issue backdating.

{% hint style="warning" %}
A full Git clone is required. If a shallow clone is found, the blame information retrieval will be skipped and the analysis may fail.
{% endhint %}

For more information on SCM integration, see [scm-integration](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/scm-integration "mention").

In addition, we recommend cloning all the branches of the repository to avoid reference errors during the checkout.

With Git, this means using `fetch-depth: 0`. This disables shallow clones and fetches all branches.

{% hint style="warning" %}

* Avoid any attempt at performing actions on the cloned repository to make sure the repository contains valid repository metadata (e.g. the .git folders have not been removed).
* The code in the cloned repository matches the code in the original repository (e.g no code is added to the branch on the cloned repository before analysis).
  {% endhint %}

## Related pages

* [Broken link](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/scanners/scanner-environment/broken-reference "mention")
* [scm-integration](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/scm-integration "mention")
* [Broken link](https://docs.sonarsource.com/sonarqube-server/2026.1/analyzing-source-code/scanners/scanner-environment/broken-reference "mention")