Repository defaults

What this controls#

Repository defaults show two repository-level values:

• Repository default branch is detected by the sync agent from the checkout and payload metadata. Syncs are accepted only when they run from that detected default branch.
• Primary framework controls which detected framework is shown first when several frameworks are present.

Primary framework is a display preference. It does not add directories, remove frameworks, or change which test files are discovered.

Default branch policy#

Test Chronicle does not require the branch to be named main. Repositories that use master, next, dev, develop, or another default branch can sync successfully when the agent reports that branch as the repository default.

Feature-branch syncs are rejected before they mutate specs, commits, snapshots, frameworks, or sync markers. The failed attempt is still visible in Activity diagnostics so you can confirm which branch was received.

Automatic behaviour#

The sync agent detects the repository default branch and sends it with each sync payload. The dashboard displays that value as the tracked branch; it is not edited from project settings.

The Repository settings page still lets maintainers choose a primary framework when a mixed project should be represented by one framework first. For example, a repository may use Vitest for most tests and Playwright for a smaller E2E suite.

Configure repository defaults#

Open Project Settings -> Repository.

1. Review the detected repository default branch.
2. Choose a primary framework or select Automatic.
3. Save repository defaults.

The primary framework preference is available to dashboard presentation after saving.

Precedence and timing#

These settings do not override test discovery directories or testing classification.

Examples#

Single-framework repository#

A Vitest repository whose default branch is main normally needs no repository overrides.

Mixed-framework monorepo#

A monorepo with 1,200 Vitest tests and 180 Playwright tests can set Vitest as the primary framework while continuing to discover and filter both frameworks.

Non-main default branch#

A repository whose default branch is next should run its sync workflow from next. A feat/new-dashboard run is rejected unless that branch is the repository default.

Reset and troubleshoot#

Select Reset to automatic, then save, to remove the primary framework override.

If syncs are rejected for the wrong branch, confirm the checkout used by the sync workflow is on the repository default branch and that the agent can detect repository metadata. If a framework is missing entirely, use Test discovery; primary framework cannot discover it.

SyncConfig fragment#

{
  "primaryFramework": "vitest"
}

Omit primaryFramework to restore automatic behaviour.