The list
Search matches the repository’s name. The tally at the bottom counts repositories by their last check: Failing, Passing or Neutral.
Connect a repository
Connect repository opens a dialog with four steps:1
Provider
The accounts already connected, one row each. In local mode, Local folder is a row of its own. See Local folders. Connecting a new account is Settings’ job, and the last row links there.
2
Repositories
What that account can see. A repository already connected is shown as connected and cannot be picked twice.
3
Context
Which of the workspace’s sources the repository reads. A source that is a picked repository’s own documentation is checked to begin with.
4
Confirm
Connect and start onboarding writes the repository and starts its Flow setup in the background.
The repository console
A repository has six tabs, in two groups. The tab rides the address, so a tab is a place you can link to.
The header carries the repository’s name, its default branch, and the verdict and time of its last check. When the workspace has no model provider, a banner says so above the tabs.
Flows are not a tab here. A flow belongs to the workspace and is listed across every repository on Flows. Documents are not a tab either: they belong to the workspace, under Context. This console’s Context tab only says which sources this repository reads.
Unlinking a repository
Unlink repository on the Settings tab disconnects it. Whatever it has in flight is cancelled. Its sources stay, because a source belongs to the workspace and losing one reader is not losing the source.Next steps
Flow setup
What starts as soon as a repository is connected.
Repositories and providers
Where accounts are connected, and which providers exist.