Repositories and lifecycle

Create a repository, share its clone URL, and manage its lifecycle deliberately.

Create and clone

A service admin can create a repository in the console. Set its display name, default branch, object format and allocation as appropriate. The service creates it through a durable operation; wait for completed before treating it as ready.

Copy the SSH URL from the repository. On a default fresh installation it resembles:

git clone ssh://git@git.example.com:2222/example-project.git

Your account needs a personal SSH key and the appropriate membership. For an empty repository, push your first branch with your usual Git client. The console does not edit files or create commits.

Names and stable identity

The display name is a label. A separate clone name determines the friendly SSH route. Changing only the display name preserves the URL. Changing the clone name retires the old named address; update clients to the new URL or use the immutable UUID route.

Repository UUIDs and physical storage paths do not change. Names remain reserved while archived or deleted. A permanently purged repository's UUID and names stay reserved forever.

Archive, delete and restore

• Archive: keeps reads available and blocks writes after draining them.
• Unarchive: returns to active after current storage checks.
• Delete: blocks all Git access and retains bytes.
• Restore: changes a deleted repository to archived, under current permissions. Unarchive separately when writes should resume.

These actions do not recover a lost disk or undo a force-push. Use full-instance recovery for disaster recovery, and protect important Git history through your own operational policy.

Permanent purge

Only a service admin can permanently purge. It requires the exact current display name, expected version and stable operation identity. The service drains sessions/jobs and durably removes the repository and its owned artifacts. Failure keeps its access fence for explicit operator recovery.

Purge is irreversible. It is never automatic or a storage-pressure remedy. Older backups may still contain the repository. Repository admins cannot perform this action.

Operations and stale edits

Creation, lifecycle and exports return durable operation records. Pending and running are not completion; HTTP 202 means accepted. Check the final completed/failed result. A stale version is rejected rather than silently overwriting another edit. Inspect a failed operation before retrying; see Status.