Skip to content
Latchkey home
Documentation menu

Managing repositories

Enable or disable monitoring per repository, understand plan limits, and know what enabling and disabling a repository do.

In short

  1. Owners and admins enable or disable repositories from Settings, Code hosts, Enrol repositories; changes apply on Save changes.
  2. Plan limits: 1 (Developer), 10 (Launch), 40 (Scale), 41+ (Enterprise).
  3. Enabling lets Latchkey run the repository's jobs; disabling stops Latchkey running its jobs and removes its knowledge base index and file layout scan.
app.latchkey.dev / acme / settings

Settings, Code hosts tab of the acme workspace: the GitHub · acme connection is Live with acme/api enrolled for Latchkey CI, and a Repositories panel offers Enrol repositories. The Manage repository monitoring dialog opens over the dimmed page. Its counter reads 1 / 10 repositories selected with a Launch plan tag, above a search box, Select all and an All visibility filter. acme/api is ticked, with its Analysis branch set to main (default) and the line Latchkey reads this branch to detect the repository's tech stack and to decide which files a heal PR may change.; acme/web and acme/worker are not ticked, and Save changes is unavailable. acme/web is ticked: the counter reads 2 / 10, the foot shows 1 pending change, and Save changes becomes available. Save changes is pressed and reads Saving with a loader. The dialog closes and a toast says Monitoring enabled on 1 repository: Latchkey CI runs a repository once it has a workflow file under .latchkey/workflows/.

FIG. 1.4-AA ticked box only queues a change: the counter counts it against your plan's limit at once, and nothing is enabled until Save changes. The Analysis branch picker shows under a repository once Latchkey already monitors it.

Latchkey only runs jobs for repositories you explicitly enable. You choose them during onboarding, and you can change them any time from Settings, Code hosts. Enabling is what makes a repository eligible for Latchkey CI and for managed runners: neither serves an unmonitored repository.

Manage repository monitoring#

Open Settings, then the Code hosts tab, and click Enrol repositories in its Repositories panel (workspace owners and admins) to open Manage repository monitoring. The header shows how many repositories you are using against your plan limit. Each repository has a checkbox; changes are queued as pending changes and applied together when you click Save changes.

  • Search and scroll: the list searches your organization live and loads more as you scroll.
  • Analysis branch: each monitored repository shows an Analysis branch picker (the repository's default branch by default). It sets the branch the Runners AI scan reads to detect the repository's tech stack, and the branch whose directories Latchkey classifies to decide which files a heal PR may change. AI Insight reads workflow files on the repository's default branch whatever the picker says, and its cost and reliability findings count runs from every branch.
  • Permissions: enabling and disabling monitoring requires an owner or admin role.

Plan limits#

PlanMonitored repositories
Developer1
LaunchUp to 10
ScaleUp to 40
Enterprise41+

At your limit, no more repositories can be ticked, and the dialog says so and points you to upgrade. On Developer, the single monitored repository cannot be swapped from the dialog; upgrading to Launch or Scale unlocks that.

Choosing repositories under a limit#

When you have more repositories than slots, treat the limit as a prioritization question:

  • Any repository whose jobs you want Latchkey to run must be monitored. Latchkey CI runs only monitored repositories, and a job targeting a latchkey-* label from an unmonitored repository gets no runner. In a repository that was never enabled, the job stays queued on GitHub until GitHub expires it, about 24 hours later; in a repository that was enabled and then disabled, Latchkey cancels its whole run, GitHub-hosted jobs in it included, once the job has waited at least 10 minutes. If running on Latchkey is the goal, those repositories come first.
  • High-activity repositories give the dashboard the most to work with. The dashboard and AI Insight's cost and reliability findings are built from the jobs Latchkey runs, so a repository that runs CI on Latchkey many times a day produces far more signal than one that builds weekly.
  • A chronically failing pipeline is a strong candidate once it runs on Latchkey. Reliability findings are computed from the runs Latchkey serves, so a flaky repository earns findings, and self-heal, only after its jobs run on Latchkey CI or a Latchkey runner. See Optimization insights.
  • On Developer, choose deliberately. The single monitored repository cannot be swapped from the dialog, so pick the repository you most want to run on Latchkey; upgrading to Launch or Scale unlocks swapping.

What happens when you enable a repository#

01
Registered
Events flow via the GitHub App (no per-repo webhook created)
02
Runner-ready
In an organization, the repository joins the Latchkey runner group
03
Feeds AI Insight
Its GitHub Actions workflow files are scanned for security findings; its runs count once Latchkey runs them

Once a repository commits its first workflow file under .latchkey/workflows/, Latchkey CI runs it on the pushes and pull requests the file's on: block names; until then, Latchkey writes no check on its commits and shows no Latchkey CI run for it.

Where a repository's figures start#

Command & Control, Runs, Performance, Cost and AI Insight count only the runs and jobs Latchkey runs, so enabling a repository adds no past runs. A repository's figures start with its first Latchkey CI run or its first job on a Latchkey runner: Runs and Cost count both, while Performance and the pipeline figures on Command & Control count only Latchkey CI runs. If a page still looks empty after that, check that the dashboard's date range overlaps the run before assuming something is wrong.

What happens when you disable a repository#

Disabling frees the slot against your plan limit. From that moment Latchkey CI starts no new run for that repository, and managed runners stop taking its jobs within about a minute. Its knowledge base index and file layout scan are removed. Its GitHub Actions run records, imported or received while it was enabled, stay stored out of your dashboard, while the minutes and cost of jobs Latchkey ran for it stay in your dashboard totals. A job in that repository targeting a latchkey-* label gets no runner, and after the job has waited at least 10 minutes Latchkey cancels its whole run.

Common questions#

Q.01What happens to a repository's data when I disable it?

The slot is freed against your plan limit, Latchkey CI starts no new run for the repository, and managed runners stop taking its jobs within about a minute. Its knowledge base index and file layout scan are removed. Its GitHub Actions run records (imported or received while it was enabled), their cost records and its AI history stay stored out of your dashboard rather than being deleted, and deleting the workspace removes them. The minutes and cost of jobs Latchkey ran for it stay in your dashboard totals, and some records expire on their own schedule (GitHub Actions job steps after 180 days, heal records, failing test records and pull request path records after 90); see Security and GitHub permissions.

Q.02What happens when I re-enable a repository?

Latchkey runs its jobs again.

Q.03Can a Member enable or disable monitoring?

No. Enabling and disabling monitoring requires an owner or admin role, and the Repositories panel on the Code hosts tab of Settings, where Enrol repositories opens the dialog, is shown to owners and admins only. Roles are described in Team and roles.

Q.04Does enabling a repository add webhooks or files to it?

No. There is no per-repo webhook created and nothing is committed to the repository; events flow through the GitHub App installed on your organization.

Q.05What does the Analysis branch picker control?

The branch the repository scan and the Runners AI scan read (the repository's default branch by default). AI Insight reads workflow files on the repository's default branch whatever the picker says, and its cost and reliability findings count runs from every branch. See Troubleshooting.

Q.06Can an unmonitored repository use managed runners?

No. Managed runners only serve monitored repositories, so a job targeting a latchkey-* label from an unmonitored repository gets no runner. In a repository that was never enabled, the job stays queued until GitHub ends it after 24 hours. In a repository you disabled, Latchkey cancels the job's whole run, GitHub-hosted jobs in it included, after the job has waited at least 10 minutes. Enable the repository from Settings, Code hosts, Enrol repositories first.