Branch-Level Scanning

Scan any branch in your repository, not just the default branch.

How It Works

When triggering a scan, you can select any branch from the dropdown in the scan trigger modal. Branches are fetched live from your connected GitHub, Bitbucket, or GitLab account, so the list always reflects your current repository state.

Scan results are tagged with the branch name, making it easy to track findings per branch.

Global Branch Selector

Every dashboard page (SCA, Quality, Security Center) includes a branch dropdown next to the repository selector. Selecting a branch filters all data to show only results from scans run against that branch. This applies to findings tables, charts, trends, and summary cards.

Branch in Scan Results

Each scan result displays which branch was scanned with a branch badge. Non-default branches are highlighted with a violet badge so you can distinguish them at a glance from default-branch scans.

Scheduled Scans by Branch

Configure scheduled scans to run against a specific branch using the trigger_branch field in scan schedule settings. This is useful for monitoring long-lived branches like develop or staging on a recurring basis.

See Scheduled Scans for setup instructions.

Default Branch Detection

When you connect a repository, CodeStax auto-detects the default branch from your SCM provider (e.g., main, master, develop) and stores it. All scans default to this branch unless you explicitly select a different one.

If your repository’s default branch changes on the SCM side, CodeStax picks up the change on the next branch fetch.

Permissions

Any user with access to the repository can trigger scans on any branch. Branch selection does not require additional permissions beyond normal scan access.