Tags and Branches

SourceClear Software Composition Analysis

SourceClear is designed to be used with Git-based systems. Within these systems, there are commits, branches, and tags. This page describes how these three items affect issues in SourceClear and how you can manage them.

How a Branch or Tag Affects Issues

SourceClear has a unique list of issues for each branch or tag scanned, which means that if you have scanned multiple branches, you may see the same issue multiple times in the issues list. This feature allows you to see the state of a specific branch or tag rather than having only one set of results for everything.

Seeing a specific branch or tag

When viewing a project within SourceClear, you can choose to see issues from a single branch or tag. To do this, click the Change button next to the Latest Branch heading. This shows you what branches you have scanned.

How SourceClear identifies the branch or tag

SourceClear chooses either a tag, branch, or commit hash when porting results into the web UI. We use the git describe --all command to determine the state of the repository being scanned. This means that the order of selection will be tag > branch > previous tag > previous branch > commit hash Note: This means that if you are scanning a tag on a branch, it will show up as a tag and NOT a branch.

Selecting a default branch

SourceClear has a unique list of issues for each branch or tag scanned. However, this means that the Issues List can get quite large. To combat this, SourceClear allows admins to set a default branch. This default branch will change the numbers seen in the Project List, Issues List, and the Project Details page.

To select the default branch for a project, use the Settings action in the top right-hand corner.