How do I get started with git.sr.ht?

Register or log in at git.sr.ht. That is the entry point: the service's own welcome page says "Register here or Log in to get started." If you already have a sourcehut account, use Log in; if you are new, use Register. Everything else — creating repositories, setting visibility, managing releases — happens after you are inside.

What git.sr.ht is

git.sr.ht is the Git hosting service for sourcehut, described on the site as "the hacker's forge." It hosts Git repositories and is one part of the wider sourcehut platform.

What you get once you are in

The service lists these features:

• Public, private, and "unlisted" repositories
• Fine-grained access control, including access for users without accounts
• Software release management

So the account is not just a login — it is what unlocks repository creation, per-repository visibility choices, collaborator permissions, and release publishing.

Steps to get started

1. Go to git.sr.ht.
2. Choose Register if you do not have a sourcehut account, or Log in if you do.
3. Complete the account flow presented to you.
4. Once inside, create a repository and set its visibility (public, private, or unlisted).
5. If you need collaborators, use the access control settings — including the option to grant access to users who do not have accounts.
6. If you publish versioned artifacts, use the release management feature.

Expected result: you have an account session on git.sr.ht and can create and configure repositories.

Common sticking points

• Mercurial users: git.sr.ht is Git only. The welcome page points to sourcehut's separate hg service for Mercurial support, so do not expect Mercurial repositories here.
• "Unlisted" vs "private": these are listed as distinct options, so pick deliberately rather than assuming unlisted means private.
• Outside collaborators: access control explicitly covers users without accounts, which matters if you work with people who will not sign up.

Quick reference