Projects and repositories

Creating a project

Open Projects → New project and enter:

• Project code — a short stable code such as ERP;
• Name — a human-readable name;
• Description;
• Visibility;
• whether access requests are allowed.

Visibility

• Private — visible only to users with permission;
• Restricted / listed — visible in lists, while content requires access;
• Public — visible according to the server's public-access policy.

Creating a repository

On the project page select New repository and enter:

• repository code such as server;
• name and description;
• default branch such as main;
• visibility;
• whether access requests are allowed.

After creation DigiVC displays a permanent repository address.

Repository page

The repository page contains:

• Browser — current file tree;
• History — revisions and commit messages;
• Locks — active locks;
• Checks — validation policy and recent runs;
• Access — repository and path roles.

Full and partial checkout

In Client Access / Checkout you can:

• copy the repository address;
• generate a full-download command;
• select one or more paths in the browser;
• open the Desktop Client.

Partial checkout example:

/backend/api
/database/sql
/docs/contracts

The Desktop Client includes required parent directories but does not download unrelated content.

Read-only and archive

• Read-only blocks new commits while allowing viewing and download according to permissions.
• Archive removes the repository from normal views without destroying history, subject to retention policy.

Critical operations require a reason and are recorded in the audit trail.

Project languages

The project page shows a detected programming-language breakdown based on visible source files. Generated, vendor, binary and lock files are excluded. This is an analytical view, not a compiler validation.