Kimura SCM

Appearance

Repository Links (Repository Map) ​

Repository links define how your local workspace folders map to server repositories and branches.

In Kimura SCM, you usually don’t work “in a repository” directly. You work in a workspace, and the repository links tell Kimura which repository/branch each part of your workspace belongs to.

What A Repository Map Does ​

A repository map is a set of mapping entries. Each entry links:

  • a local Path (folder in your workspace),
  • to a server Repository,
  • and a Branch within that repository.

The workspace tree and most operations (history, reconcile, submit, sync) depend on these mappings to know where files live on the server and which branch they target.

Repository links let you:

  • Work on the right branch without moving local folders around.
  • Split one workspace into multiple repositories (or multiple branches) when needed.
  • Share a consistent mapping with teammates (so everyone’s workspaces line up).

One Repo, One Branch (Most Common) ​

Your workspace root maps to a single repository and branch (for example MyGame + main). This is the simplest setup.

One Workspace, Multiple Repositories ​

Some teams keep separate repositories for separate components (for example Engine, Game, Plugins, Raw Assets). A repository map can map different local folders to different repositories.

One Workspace, Multiple Branches ​

You can map different local folders to different branches (for example a release branch for one area and a development branch for another). Use this carefully; it’s powerful but can be confusing if you’re not expecting it.

  • History: can show and filter by Repository and Branch.
  • Submitting: when you submit a change list, Kimura applies each file operation to the repository/branch determined by the map entry that owns that file’s path.
  • Syncing: sync targets the repository/branch for your selected item.

Repository Maps vs. Permissions ​

Repository links tell Kimura “where” something belongs, not “who can do what”. If you can’t see or modify parts of a repository, it’s usually controlled by group access.

In the Visual Client:

  • Create workspace: you pick an initial Repository map.
  • Repository links tab: you can view/edit mappings, apply changes to the workspace, and share mappings.