Teams & repos

Team KPIs are scoped to the repositories you assign here. GitHub imports team names and members, but not which repos belong to which team — you define that in DeliveryCompass so metrics match how your org actually works.

1. Open Teams & repos from the top navigation.
2. Each card represents a GitHub team imported into your workspace.
3. Drag repositories from the Unassigned pool onto a team card.
4. Changes save automatically. Refresh the dashboard to see updated team KPIs.

• One team per repository. A repo can belong to at most one team for KPI scope. Dragging it to another team reassigns it.
• Unassigned repos are synced but not compared. They count toward organization metrics only until you map them.
• New repos appear after sync. When GitHub adds repositories, they show in the unassigned pool after the next daily import.
• Archived repos and forks are excluded from ingestion and do not appear in the pool.

If team cards show empty KPIs, check that repos are assigned and that bootstrap has finished. See troubleshooting: team KPIs missing.

Overview and organization KPIs include every ingested, non-excluded repository — even unassigned repos.

Team cards and Team analytics only include repositories you mapped to that team. This is intentional: many GitHub orgs do not maintain accurate team-to-repo links.

GitHub team membership is imported for labels and weekly tables, but does not drive which PRs count toward a team’s throughput.