Repository defaults

What this controls#

Repository defaults contain two independent settings:

• Default branch controls the branch used when Test Chronicle scopes repository history and builds source-file links.
• Primary framework controls which detected framework represents the project 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.

Automatic behaviour#

With no overrides, the sync agent detects the repository's default branch and Test Chronicle uses the detected framework list.

The Repository settings page shows the effective value and labels it Automatic or Custom override.

When to add an override#

Set a custom default branch when:

• The checkout does not expose the expected repository default.
• Historical analysis should follow a long-lived branch other than the detected default.
• Source links should open a specific branch.

Set 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 effective branch and primary framework.
2. Enter a repository branch name or leave the branch blank for automatic detection.
3. Choose a primary framework or select Automatic.
4. Save repository defaults.

A branch override affects sync behaviour on the next run. 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 on 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.

Release branch history#

Set release as the default branch when the project intentionally tracks test history from that branch instead of the repository default.

Reset and troubleshoot#

Select Reset to automatic, then save, to remove both repository overrides.

If history follows the wrong branch, confirm the branch exists in the checkout used by the sync workflow and that GitHub Actions checks out full history. If a framework is missing entirely, use Test discovery; primary framework cannot discover it.

SyncConfig fragment#

{
  "defaultBranch": "main",
  "primaryFramework": "vitest"
}

Omit either field to restore automatic behaviour for that setting.