# Viewing your first analysis' results

If you have successfully followed the in-product tutorial, SonarQube Cloud 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.

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.

## Overview page

Once your analysis is completed a project Overview page opens, displaying the **Project health dashboard**, a built-in Sonar dashboard available in all plans. Custom dashboards and other built-in dashboard views are available in the [Enterprise](https://www.sonarsource.com/plans-and-pricing/sonarcloud/) plan.

<figure><img src="https://2223713658-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB4UT2GNiZKjtxFtcFAL7%2Fuploads%2FbftTYtT6HWGh5SAFOeFa%2Fproject-first-analysis-overview-dashboard.png?alt=media&#x26;token=8db4d52e-a5e2-4fb9-96e3-fb8326a0bdaf" alt=""><figcaption></figcaption></figure>

The top row of the dashboard shows:

* **Quality gate status**: Passed, Failed or Not Computed.

{% hint style="info" %}
**The quality gate displays Not Computed because it needs to be configured.**

We strongly recommend set a new code definition by goin to *Your project* > **Administration** > **New Code**.

See the [quality-gates](https://docs.sonarsource.com/sonarqube-cloud/standards/quality-gates "mention") and [about-new-code](https://docs.sonarsource.com/sonarqube-cloud/standards/about-new-code "mention") 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**.
{% endhint %}

* **Open issues**: 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.

{% hint style="info" %}
**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 [overview](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/test-coverage/overview "mention") section.

Once it’s configured, push a change to the main branch to update the analysis. After the a new analysis is run, the coverage percentage will be displayed.
{% endhint %}

See [retrieving-projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/retrieving-projects "mention") for more information about the Project health dashboard and other project related information.

## Main branch <a href="#main-branch" id="main-branch"></a>

To view additional information about the most recent main branch analysis. Go to *Your project* > **Summary** page. Alternatively, you can go to *Your project* > **Branches** and select the main branch from the list of all the branches. See [main-branch-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/branch-analysis/main-branch-analysis "mention") for more information.

## Pull Requests <a href="#pull-requests" id="pull-requests"></a>

In addition to analyzing your main branch every time it changes, SonarQube Cloud 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.

To view a pull request analysis go to *Your project* > **Pull requests** and select your pull request from the list. See [pull-request-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/pull-request-analysis "mention") for more information.

## Branches <a href="#branches" id="branches"></a>

The **Branches** page displays all the non-pull request branches for which you have set up analysis. Go to *Your project* > **Branches** to view the list. 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. See [branch-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/branch-analysis/branch-analysis "mention") and [branch-analysis-setup](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/branch-analysis/branch-analysis-setup "mention") for more information.

## Related pages

* [retrieving-projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects/retrieving-projects "mention")
* [main-branch-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/branch-analysis/main-branch-analysis "mention")
* [pull-request-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/pull-request-analysis "mention")
* [branch-analysis](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/branch-analysis/branch-analysis "mention")
* [branch-analysis-setup](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/branch-analysis/branch-analysis-setup "mention")