Skip to main content

Overview

Default branch filters control which branch refs appear when a table is scoped to the default ref view. They help teams focus default views on the branches that matter most for triage, reporting, and dependency review. The setting affects:
  • Vulnerability list view through the Ref scope filter, where the default option is Default branches.
  • Manifests through the Ref scope filter, where the default option is Default refs.
  • Repository overview widgets that use default reference scope.
Users can still switch supported tables to All branches or All refs when they need broader coverage. In the vulnerability list view, selecting specific Branch or Tag references narrows results to those refs and takes precedence over the default branch scope.

Where To Configure

Default branch filters can be configured at multiple scopes:
ScopeLocation
WorkspaceSettings > References
OrganizationOrganization Settings
RepositoryRepository Settings
Repository settings inherit from the organization hierarchy, then workspace settings, then the global default. A more specific setting takes precedence over inherited settings.

Options

The Default branch filter setting includes these controls:
OptionPurpose
Include default branchAlways include the repository’s default branch
Specific branchesInclude exact branch names
Branch patternsInclude branch names that match wildcard patterns
The default configuration includes the repository’s default branch.

Branch Patterns

Branch patterns accept comma-separated values. Exact branch names also work in Branch patterns. Wildcard behavior:
Pattern characterMeaning
*Matches any sequence of characters
?Matches one character
Examples:
PatternMatches
release/*Branches under release/
hotfix-*Branches that start with hotfix-
mainThe branch named main

Empty Default Views

If Include default branch is turned off and no Specific branches or Branch patterns are selected, the default ref view hides matching records by default. Use that configuration only when the intended default view should start empty until a user switches to All branches or All refs. If a repository has no recorded default branch and Include default branch is enabled, Cysmiq avoids filtering out the repository solely because the default branch is missing.

How Views Use The Setting

In the vulnerability list view, Default branches scopes findings to resolved default refs. When the view is focused on active statuses, Cysmiq uses currently unfixed locations for that default branch scope. The table also keeps directly accessible vulnerability records visible for users who have direct vulnerability access. In the manifest view, Default refs scopes manifests to the resolved default branch refs for accessible repositories. Switch Ref scope to All branches or All refs to include refs outside the configured default set. Use the Branch or Tag filters in the vulnerability list view when you need to focus on named refs.