Kimura SCM

Appearance

Repositories ​

A repository is a top-level project container on the Kimura SCM server. It holds your project’s folders and files and keeps their history over time.

Most day-to-day work in Kimura revolves around the relationship between:

  • Repository: the server-side container for a project.
  • Branch: a named line of work inside a repository (for example main).
  • Workspace: your local working area, mapped to one or more repository/branch pairs.

Kimura repositories are designed to handle very large numbers of files, and there are no limitations on file sizes.

How Repositories Are Used ​

Repositories And Workspaces (Repository Map) ​

You do not “open a repository” directly. Instead, you create a workspace and connect parts of your local folder tree to repositories/branches using a repository map.

In practice, that means:

  • Each mapping entry links a local path to a specific Repository and Branch.
  • Your workspace view is built from those mappings.

Where to manage this in the Visual Client:

Repositories, Revisions, And History ​

Kimura tracks changes on the server as revisions. As you submit work, the repository accumulates history:

  • The History tab can filter and display revisions by Repository and Branch.
  • You can sync your workspace to a specific revision when needed.

Repositories And Access Control ​

Repositories are usually protected by group permissions:

  • Who can see a repository, and what they can do inside it, is managed through Administration → Groups access rules.
  • Access can be set at different levels (repository/folder/file) depending on what’s selected in the access view.