CodeCargo logo

Platform

Repositories

The Repositories page lists every GitHub repository in your organization that the CodeCargo GitHub App can see. Here you choose which ones CodeCargo works with, turn guardrails on or off, and scan repositories for the Service Catalog.

Find it under Build → Repositories in the organization sidebar.

The Repositories page for Acme Corp: 12 of 25 active repositories allowed in plan and 6 inactive, Refresh and Add repositories in the header, the Active tab with a search box, and a table of repositories with their description, guardrails and service catalog status, and the viewer's GitHub role

Active and Inactive Repositories

CodeCargo works only with active repositories. It reads an active repository's workflows from GitHub and keeps them in sync, so they appear across the app: in Workflows, Compliance, the Service Catalog and CargoWall. You can link an active repository to a project or add it to your workspace. Repositories that aren't active wait on the Inactive tab. CodeCargo lists them, but doesn't read or evaluate their workflows. When nothing is active yet, the page opens on the Inactive tab.

The header shows how many repositories are active against your plan's limit, for example 12 of 25 active repositories allowed in plan, and how many are inactive. The count is flagged as a warning once you reach the limit. That count includes active repositories you can't access, so it can be higher than the Active tab, which lists only the repositories you can see, and those repositories can be what fills the limit. On a plan with no limit, the header shows only the number of active repositories you can see.

The Inactive tab listing six repositories under a note that some repositories are activated for you and count toward the plan's limit of 25. Each row has a checkbox, an activate icon before the repository's name, its description and the viewer's GitHub role, with a select-all checkbox in the header

Activating a Repository

Open the Inactive tab and click the activate icon before the repository's name, or choose Activate from the row's ⋯ menu. CodeCargo reads the repository's workflows from GitHub straight away, and the repository moves to the Active tab.

CodeCargo won't activate a repository when:

  • Your organization is at its plan's limit. You'll see Active repository limit reached. Deactivate a repository before you activate another.
  • The repository is empty. A repository with no commits can't be activated until something is pushed to it.

Repositories also become active on their own when CodeCargo works in them: when you link them to a project or add them as a Building Block source, when a migration that uses them starts, when an agent works in them, or when a CargoWall job runs in them. Each counts toward your plan's limit, and none of these activates a repository once the limit is full. When you first set up CodeCargo, you activate your first repositories from Pick your first repositories (see Onboarding Sync).

Activating Several Repositories

If you have the organization Admin role, the Inactive tab has a checkbox on each row. Tick the repositories you want and click Activate N repositories. The button appears once one is selected, and the label includes the count, for example Activate 3 repositories. The checkbox in the column header selects every repository the current search shows, on every page, and no others.

They activate one after another. The button shows progress, for example Activating 2 of 6…, and the ones that activated move to the Active tab when the run is done. You can't start another activation until then.

A full plan or an empty repository still can't be activated. If the plan's limit is reached partway through, the run stops and reports a partial result, for example Activated 4 of 6 repositories. 2 hit the plan's limit. Any other failure is named, and the run continues. Repositories that didn't activate stay selected.

Deactivating a Repository

Choose Deactivate from the row's ⋯ menu and confirm. CodeCargo stops tracking the repository: its workflows are no longer scanned or evaluated, and it no longer counts toward your plan's limit. Nothing changes on GitHub, and you can activate the repository again at any time.

You can't deactivate a repository that is linked to a project or is a Building Block source. Remove it from the project or source first.

Who can make changes

Activating and deactivating repositories, turning guardrails on or off, and starting a service catalog scan need the organization Admin role. Everyone else can browse the list. See Access Control.


Guardrails and Service Catalog

On plans that include AI features, the Active tab has two status columns. Each column header has a filter, so you can narrow the list to one status.

Guardrails shows whether CodeCargo evaluates the repository's workflows against your organization's compliance rules. A green shield means guardrails are on, and a gray one means they're off. Click the shield to switch. With guardrails on, CodeCargo evaluates the repository's workflows automatically, except any workflow you've turned off on its own. Evaluations use AI. Guardrails are off for a repository until you turn them on, either here or for a whole project with Automatic Scanning.

Service Catalog shows whether the repository has been scanned to detect its services, components and dependencies for the Service Catalog:

IconStatusWhat you can do
Green checkScannedRe-scan from the ⋯ menu (Scan Services)
SpinnerScanningWait. The page updates when the scan finishes
Dashed squareNot scannedClick the icon to scan the repository
Red alertFailedHover for the reason, then click the icon to retry

A scan that hasn't progressed in 30 minutes is treated as stuck. It shows the red alert, and you can retry it. Re-scanning a scanned repository stays in the ⋯ menu so it isn't started by accident: a scan uses AI, and components the new scan no longer finds are removed from the catalog along with their annotations. Public forks can't be scanned.


Finding and Opening Repositories

  • Search matches a repository's name, description or default branch. Showing n of m counts the matches on the current tab.
  • Name opens the repository's page, with tabs for its workflows, CargoWall and, on plans that include AI features, Compliance and the Service Catalog. The badge next to the name is its default branch.
  • Your Role is your own permission on the repository in GitHub: Read, Triage, Write, Maintain or Admin.
  • The + at the start of an active row adds the repository to your workspace for the GenAI Editor. Sort that column to bring the repositories already in your workspace to the top.
  • The ⋯ menu has Open in GitHub, and the scan, guardrails and activation actions described above.
The options menu open on cart-ui with Open in GitHub, Scan Services, Enable guardrails and Deactivate

Missing Repositories

If a repository you expect isn't listed, the CodeCargo GitHub App can't see it.

Click Add repositories, next to Refresh, to open the app's repository access on GitHub and include it. On GitHub Enterprise, that page opens on your organization's GitHub rather than github.com. If the app isn't installed yet, the button opens the install page instead. When no repositories are listed at all, the same button is in the empty state.

Only a GitHub organization owner can change that access. If you aren't one, Add repositories is disabled, and its tooltip asks you to have an owner add the repositories. The organization Admin role in CodeCargo doesn't grant this.

When you come back from GitHub, CodeCargo refreshes the list and opens the Inactive tab, where newly added repositories appear. Ones added on that visit are marked New until you leave the page or reload it. They stay inactive until you activate them.

Refresh asks GitHub again which repositories you can access. It runs in the background and shows its progress at the top of the page. To resync the whole organization, including members, use Resync Organization in Org Settings (see Manual Repository Sync).


What You Can Do Next