Skip to content
KurrentDB

Sessions & repositories

Open General → Sessions (/admin/settings/sessions) for default visibility and repository attribution. The former /admin/settings/general page redirects here. GitHub authentication health is on Integrations.

In Org-visible sessions, enter comma-separated GitHub organization or user names in Repo owners (Optional), then click Save. Sessions in those owners’ repositories default to organization-visible.

A blank value uses the connected GitHub account when one is available. Otherwise, sessions with default visibility remain private. This setting is Visibility:AutoPublicRepoOwners.

This configures the default; session owners can still make explicit sharing choices. See Visibility & sharing.

Repo attribution backfill attempts to attach a repository to sessions recorded without one.

  1. Click Dry run to inspect candidate matches without writing changes.
  2. Review the counts for matched, ambiguous, unresolved, inadmissible, deduplicated, and errored sessions. The report also groups matches by attribution tier and repository.
  3. Click Backfill and confirm to attach the best-effort matches.

Only one sweep can run at a time. If a sweep is already active, try again after it finishes.

Open Repositories → Repositories (/admin/repositories) when repository grouping is available on your deployment. Aliases group a renamed or forked repository under a canonical repository identity, so its sessions, evaluations, and work items appear together in read views.

For a detected GitHub rename, review Pending suggestions and choose Confirm to create the alias or Dismiss to clear the suggestion.

To add one manually, enter the Member repo hash and Canonical repo hash under Add an edge, then click Add. Both are 16-character lowercase hexadecimal hashes. Existing links appear in Alias graph, where Remove deletes an alias link.

Repository aliases describe repository identity; Projects group distinct repositories that belong to the same work.