Repositories

A repository is a single SVN repository managed by subforge. It lives under a workspace — either your personal workspace or an org workspace — and can be browsed, cloned, and committed to via any SVN client.

Creating a repository

Click + New repo from your workspace page or the top nav, then fill in:

• Workspace — which workspace to create the repo in (your own or an org workspace you manage).
• Name — must be 2–41 chars, lowercase letters/digits/hyphens, starting with a letter. This becomes part of the URL and SVN path.
• Description — optional, shown on the repo card.
• Visibility — Private (default) or Public. See Permissions for what this means.

A fresh repo is initialised with /trunk, /branches, and /tags directories already created.

Browsing a repository

Each repo has three tabs:

• Code — file tree at the latest revision, plus a README rendered inline if one exists. The Clone button shows the SVN checkout URL.
• History — a chronological list of every commit. Click a row to see the full changeset.
• Settings — visible to workspace owners and admins (see below).

Within Code you can navigate directories, view file contents, and browse old revisions via the Browse link on any history row.

Clone URL

The SVN checkout URL is always shown on the Code tab via the Clone button:

svn checkout https://subforge.sh/svn/<workspace>/<repo>

All standard SVN clients accept this URL. Your subforge username and password are the credentials.

README rendering

If the repository contains a README.md at the root or in /trunk, it is rendered on the Code tab.

Settings

The Settings tab is available to workspace owners and admins. From there you can:

• Edit description — change the one-line description shown on the repo card.
• Visibility — toggle between public and private.
• Collaborators — add or remove individual users or entire groups. Each collaborator has a role: read or read & write. Change a collaborator's role inline using the role selector without leaving the page.
• Rename — change the repo's name. The old name is kept as a redirect for 30 days so existing working copies don't immediately break.
• Transfer — move the repo into a different workspace you have access to.
• Archive — mark a repo read-only for everyone. Commits are blocked; the repo remains fully browseable. Unarchive to allow commits again.
• Delete — permanently removes the repo and all its history. This cannot be undone.

Naming rules for repo names

The following names are reserved and cannot be used as repo names: new, repos, members, settings.