Sessions and repositories

Org-visible sessions: General → Sessions

Repo owners is a comma-separated list of GitHub organisation or user names. A session in one of their repositories, stored with the org_public default, is readable by everyone in the organisation. Blank uses the connected GitHub account; with neither, org_public sessions stay private. Members can still share or narrow any session themselves. The setting is Visibility:AutoPublicRepoOwners

Sessions with no repository

Repo attribution backfill attaches a repository to sessions stored without one. Dry run reports matched, ambiguous, unresolved, inadmissible and deduplicated sessions by tier and repository; Backfill applies the matches after confirmation. One sweep runs at a time

Renamed and forked repositories: Repositories → Repositories

An alias groups a renamed or forked repository under a canonical one, so its sessions, evaluations and work items read as one history; stored coordinates are never rewritten. Detected GitHub renames appear under Pending suggestions with Confirm and Dismiss. Add one by hand with the member and canonical repository hashes (16 lowercase hex characters each); Alias graph lists existing links with Remove

Aliases are about identity. For distinct repositories that belong together, members make a project