If you have successfully followed the in-product tutorial, SonarCloud will run its first analysis on your project.
The first analysis is always a main branch analysis (an analysis of the default branch of your repository, usually called
From now on, a new analysis will be triggered every time you make a change to the main branch by direct push, pull request merge, or branch merge.
The first thing that appears is the Overview of your project:
Main branch status
The Main Branch Status is the quality gate of your main branch, indicating whether it meets your quality requirements and is ready to be released.
The quality gate displays Not Computed because it needs to be configured.
We strongly recommend that you set up your main branch quality gate. To do so, you must set a new code definition. Click Set New Code Definition to get started.
See Quality Gates and New Code Definition for more details. Once you set it up, push a change to the main branch. A new analysis will run, and the quality gate status will display either Passed or Failed.
Main branch evolution
The Main Branch Evolution displays a summary of the code quality results from the main branch analysis.
Findings displays the number of issues found in the main branch.
Duplications displays the percentage of main branch code that is duplicated.
Coverage displays the percentage of testable code in the main branch that is covered by your test cases.
Coverage displays zero percent because it needs to be configured.
Initially, your coverage will display zero percent because it requires configuration. To set it up, see the Coverage section.
Once it's configured, push a change to the main branch. A new analysis will run, and the coverage percentage will be displayed.
The historical data chart shows the progress of your code quality.
To see historical data, you must have run at least two analyses.
Push a change to your main branch. A new analysis will run, and the historical data will be displayed.
The Latest Activity section displays a feed of all analyses that have been run, including main branch analyses, pull request analyses, and branch analyses.
The project navigation on the left lets you move between the four views: Overview, Main Branch, Pull Requests, and Branches.
Select Main Branch to see a more fine-grained view of your most recent main branch analysis.
In addition to analyzing your main branch every time it changes, SonarCloud also analyzes individual pull requests. These analyses run when a pull request is opened and on each change to the pull request branch. This all happens before you merge, letting you catch problems before they even get to the main branch. The results of pull request analysis are displayed in the Pull Requests view of your SonarCloud project and the pull request view of your DevOps Platform (GitHub, Bitbucket Cloud, Azure DevOps, or GitLab).
The Branches view displays all the non-pull request branches for which you have set up analysis. Initially, only the main branch is listed here. But, you can configure other branches to be analyzed. Once a branch is configured, an analysis is run on every change to that branch.