> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.md).

# Branches & Baselines

The **Branches & baselines** tab of Code Analysis lists your repositories with their baseline branch, and every branch and pull request under them, with the latest quality gate and open findings. From a row you open the branch's dossier.

Open it from **Workspaces** → **Code Analysis** → **Branches & baselines** in the sidebar.

{% hint style="info" %}
Requires the **Code Analysis** licence.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FzfLeUSSC5sOn12fxpgee%2Fv2-code-bb-list.png?alt=media&amp;token=8af09062-8149-431d-878c-7acb841100ee" alt="Applications and versions table grouped by application with source, scope, quality gate and open findings"><figcaption><p>Branches and baselines</p></figcaption></figure>

## Filters, tiles and charts

The filter bar, **Filters** panel and metric tiles are the same as on the [Overview](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/overview.md#filters) tab. While no asset type is selected, **Assets by type and quality gate** and **Top rules behind Critical + Blocker findings** sit above the list.

When you choose the Mule or API asset type and your role can use AI assistance, **Code with AI** opens the AI-assisted generation of a new application.

## Applications and versions

| Control            | Description                                                                                                     |
| ------------------ | --------------------------------------------------------------------------------------------------------------- |
| **By application** | One row per repository, showing its baseline branch. Expand a row to list its other branches and pull requests. |
| **Every branch**   | One row per branch or pull request.                                                                             |

Search, **Refresh**, **Columns** and **Export** work as described in Workspaces.

| Column                     | Description                                                                                                                          |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Application · baseline** | Repository name, baseline branch and asset type. A tag shows the number of branches. Click the name to open the dossier.             |
| **Source**                 | **Bitbucket**, **GitHub**, **Design Center** or **CLI / upload**.                                                                    |
| **Scope**                  | Organization and environment.                                                                                                        |
| **Quality gate**           | **Passed**, **Failed**, **Not evaluated** or **No scan**. **Refresh requested** means a new assessment was requested.                |
| **Open findings**          | Open findings in the latest assessment, with the Critical + Blocker count.                                                           |
| **Latest evidence**        | When the latest assessment was recorded. Sortable; newest first by default.                                                          |
| **Actions**                | **Deprecate application** (when your role can manage deprecations) and **Manage application** (opens the dossier on **Management**). |

The baseline is the repository's default branch: the branch the repository list shows and its reports count. It is set from the first scan or the repository's default branch, and you can choose another in the dossier's **Management** panel.

## Branch dossier

Click a repository or branch name to open its dossier in a drawer; **Open full dossier** opens it as a full page. **View in drawer**, **Copy dossier link** and **Back to workspace** sit at the top of the full page.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F6oMJHJrG0jRtR7HzwVvp%2Fv2-code-bb-dossier.png?alt=media&amp;token=e06fdf70-f874-44b0-9136-123014ee2c46" alt="Repository branch dossier with branch picker, risk strip and panel tabs"><figcaption><p>Repository branch dossier</p></figcaption></figure>

### Header

| Item                      | Description                                                                                                                                        |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Subtitle                  | Organization, branch (or pull request with source and target), commit and current branch.                                                          |
| **Manage**                | Opens the **Management** panel.                                                                                                                    |
| **Actions**               | **Link applications**, **Deprecate application**, **Review this application** (AI review) and **Exceptions**. Items you cannot use are not listed. |
| **Investigate issues**    | Opens the findings of this branch.                                                                                                                 |
| **Branch / pull request** | Switches to another branch or pull request of the same repository. Shows the gate and assessment date.                                             |

The metric tiles show **Open finding occurrences**, **Critical + Blocker occurrences**, **Branches & pull requests** and **Recorded assessments**.

### Panels

| Panel                                         | Description                                                                                                                                                                                                   |
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AI focus report**                           | The latest AI review of this assessment, or how to request one. See [AI Focus Report](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/ai-focus-report.md). |
| **Posture & evidence**                        | The change decision against the baseline, why the gate failed, the findings that need a decision, where the findings are concentrated and the assessment surfaces.                                            |
| **Native findings** (**Findings** without AI) | The findings of this branch, as on the [Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/findings.md) tab.                                        |
| **App Inventory**                             | The latest values the metric rules recorded.                                                                                                                                                                  |
| **Code & configuration**                      | Files with findings and their history.                                                                                                                                                                        |
| **Dependencies** and **Risk & lifecycle**     | Recorded dependencies and lifecycle risks. Shown with Dependency Insights.                                                                                                                                    |
| **Assessments**                               | Assessment progression, comparison of two assessments and the assessment history.                                                                                                                             |
| **Branches & pull requests**                  | **Branch comparison**: every branch and pull request of the repository with its gate. Use **Mark as the current branch** to choose the current branch manually; click the mark again to undo it.              |
| **Management**                                | Settings for this branch, below.                                                                                                                                                                              |

### Management

The **Management** panel works as for Platform Analysis applications, worded for branches: **Default branch**, **Request fresh evidence**, **Assessment settings** (**This branch** or **All branches and pull requests (application default)**) and **Update subscriptions**. Code Analysis adds:

| Action                                          | Description                                                                                |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Review branches**                             | Opens **Branches & pull requests**.                                                        |
| **Migrate Organization**                        | Moves the repository to another organization.                                              |
| **Merge Application**                           | Merges this repository with another application.                                           |
| **Delete this branch** / **Delete application** | Permanently deletes the branch, or the repository with all its branches and pull requests. |

{% hint style="danger" %}
Deleting a branch or an application cannot be undone. The delete buttons are shown only when your role can delete applications of this type.
{% endhint %}

## Scan a branch from your pipeline

Branches with the **CLI / upload** source come from the CLI, run in your CI/CD pipeline or on a workstation. The CLI reads a security token that you generate in Security Credentials; keep it in a masked CI secret.

```bash
export IZ_CLI_VERSION=<CLI version>
export IZ_ACCESS_TOKEN=<token generated in IZ Suite>
curl -fsSLo iz.zip "https://iz-releases.s3.amazonaws.com/iz-scan-cli/$IZ_CLI_VERSION/iz-scan-cli-$IZ_CLI_VERSION-linux.zip" && unzip -oq iz.zip
./iz-scan-cli-$IZ_CLI_VERSION-linux/bin/iz-scan-cli -serviceHost "https://izsuite.example.com" -authToken "$IZ_ACCESS_TOKEN" -applicationKey "orders-eapi" -source . -scmBranchName "main" > iz-scan.log 2>&1 || true
cat iz-scan.log
grep -q "QUALITY GATE STATUS:: PASSED" iz-scan.log
```

| Option            | Description                                                              |
| ----------------- | ------------------------------------------------------------------------ |
| `-serviceHost`    | The address of your IZ Suite.                                            |
| `-authToken`      | The security token.                                                      |
| `-applicationKey` | The unique key of the application; the repository name is a good choice. |
| `-source`         | The project folder. Defaults to the current folder.                      |
| `-scmBranchName`  | The branch being analyzed.                                               |

The last line fails the pipeline step when the quality gate did not pass. **Setup** → **Scan in your CI/CD pipeline** generates the complete step for Bitbucket Pipelines, GitHub Actions, GitLab CI, Jenkins and Maven; see Setup. The full list of CLI options is in the [CLI guide](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite-legacy/iz-scan/ci-cd-integration/using-iz-scan-cli).

## Next Steps

* [Pull Requests](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/pull-requests.md): review the gate of each pull request.
* [Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/findings.md): investigate findings across branches.
* [Manage Scanning](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/manage-scanning.md): choose the repositories to scan.
* [Code Analysis](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis.md): back to the workspace.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/code-analysis/branches-and-baselines.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.
