What the Repositories tab is
Each row is a repository Leanmote found in one of your code integrations — GitHub, GitLab, Bitbucket or Azure DevOps.
With Automatic activation on, a new repo is already being measured when you see it, and your job is to switch off what shouldn't be. With the setting off, it sits paused until you switch it on.
Columns
Repository — owner/name. The namespace it lives in, who detected it and when travel with the name rather than taking columns of their own.
Tool — the integration it came from.
Teams — which teams work in this repo. Built from the recent activity, so it fills in once Leanmote reads the repo.
Last activity — the most recent push, and the author of its last commit. Only pushes move this date: a repository that only saw pull-request comments or metadata edits keeps its old timestamp, which is deliberate — it answers "is code still landing here?", not "is anyone around?".
Status — Measuring, Paused or Switched off.
View activity opens the last five activities, read live from the provider. On a repo that isn't active yet it says so: Leanmote doesn't pull data from it until you activate it, so what you see there doesn't count towards metrics. It's the fastest way to tell a live repo from an abandoned one before deciding.
Actions
Measure
Starts measuring the repo. If it was never active, Accept and load data asks how much history the initial extraction should include — 1 month, 3 months, 6 months or 1 year — and Confirm and load data queues it. Its commits and pull requests count towards metrics from then on.
Do not measure
Extractors skip it from now on. Nothing already collected is deleted, and the row moves to Switched off, where Measure brings it back.
In bulk
Tick the rows, or Select all N in this tab, and apply Measure or Do not measure to all of them. It runs in the background and an Undo appears right after.