Portfolios

A portfolio groups an index repository and its member repositories. Each member has independent sessions, Files, and Source. The root remains a workspace for the index itself.

Before you begin: connect GitHub and choose the repository that describes the collection. The setup wizard shows the destinations before cloning.

Bring in a portfolio

1. Choose New portfolio… in Projects or Profile. In Manage GitHub…, Use as portfolio… begins with that repository selected.
2. Pick the index repository and give its folder a name, such as code.
3. Select the member repositories.
4. Review the destinations and choose Create portfolio.

Members normally live at code/owner/repository. If the index is already checked out in the named folder, Space registers it without cloning it again. You can leave the dialog while cloning continues; Projects shows the progress.

You should see: a portfolio in the sidebar with a member count. Expand it to enter a member workspace. Kin may ask for a separate trust decision when you begin work in each workspace.

Resume interrupted setup

Each repository reports its own outcome. A failure keeps the setup request and files. Choose Resume portfolio…, then Retry failed, after resolving the connection or destination problem. Completed members are not cloned again.

Wait for an active setup to finish before starting another portfolio. Avoid deleting folders just to clear a failed attempt; inspect the retained result first.

Add or remove a member

Add repositories… can add more repositories and offer existing repository roots found inside the portfolio for explicit registration. Nested directories such as reference/ remain ordinary files until deliberately registered.

The remove control on a member drops its portfolio registration and keeps its files. It is not file deletion. Inspect Files separately if you intend to remove the actual checkout.

Use Ctrl+K / ⌘K to search for a member by name or portfolio/owner path. See Projects and workspaces for work inside each member.