Tutorials

Step-by-step walkthroughs for common subforge scenarios.

Tutorial 1: Create your first repo and check it out

1

Sign in and click + New repo in the top nav (or go to /new).

2

Choose your personal workspace. Enter a repo name (e.g. my-project), an optional description, and choose Private. Click Create.

3

On the Code tab, click Clone and copy the checkout URL.

4

In a terminal, check out the repo:

svn checkout https://subforge.sh/svn/<yourname>/my-project

Enter your subforge username and password when prompted.

5

Add a file and commit:

cd my-project/trunk
echo "Hello, subforge" > hello.txt
svn add hello.txt
svn commit -m "Add hello.txt"
6

Refresh the repo Code page in your browser — your commit appears in the file tree and History tab.

Tutorial 2: Set up a shared team workspace

1

Go to /orgs/new and create an org workspace (e.g. platform-team). You are the workspace owner.

2

Open the workspace page at /platform-team and go to the Members tab. Click + Add member, search for your teammates, and grant them read & write access. They now have access to all repos you create in this workspace.

3

Go to /new and choose platform-team as the workspace. Create a repo named backend. All workspace members can immediately check it out and commit.

4

Each team member checks out using the same URL format: https://subforge.sh/svn/platform-team/backend, authenticating with their own username and password.

Tutorial 3: Import an existing SVN repo

1

Go to /new. Enter the repo name and choose the target workspace.

2

Check Import from URL and paste the source SVN URL. If you want existing working copies to work without a fresh checkout, enable Preserve UUID.

3

Click Start import. The repo page opens and shows import progress. Large repos may take several minutes.

4

Once complete, if UUID was preserved, share the relocate command with your team:

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

Otherwise, everyone needs a fresh svn checkout.

Tutorial 4: Give a contractor read-only access to one repo

1

If the contractor doesn't have a subforge account yet, direct them to sign up at subforge.sh/signup.

2

Open the target repo's Settings tab. Under Collaborators, click + Add collaborator.

3

Search for the contractor's username, choose role read, and click Add.

4

The contractor can now check out the repo and browse its contents, but any commit attempt will be rejected. When the engagement ends, remove them from the Collaborators list.

Tutorial 5: Make a repo public

1

Open the repo's Settings tab.

2

In the Visibility section, click Make public and confirm. The repo is now world-readable — anyone can browse it on the web or check it out via SVN without authenticating.

3

To revert, go back to Settings and click Make private. Public read access is revoked immediately.

Tutorial 6: Onboard a new team member

1

Ask the new team member to sign up at subforge.sh/signup and share their username with you once registered.

2

Open your workspace's Members tab and click + Add member. Search for their username and grant the appropriate role (read & write for most team members).

3

They now have access to all repos in the workspace. Share the checkout URLs for any repos they need — they use their own username and password as SVN credentials.

4

For fine-grained control, create a group from the workspace's Groups tab and add team members to it. Then add the group as a collaborator on specific repos instead of granting workspace-wide access.