GitCritter

Documentation

A short tour of GitCritter. If you've used any other Git host, most of this will feel familiar.

Getting started

Sign up at /signup, then either upload an SSH public key or create a personal access token. You'll need one of those to push.

SSH keys

Generate a key locally, paste the public half into Settings → SSH, and you're done.

ssh-keygen -t ed25519 -C "you@example.com"

Then copy ~/.ssh/id_ed25519.pub into the form.

Personal access tokens

For HTTPS pushes and API calls, mint a token in Settings → Tokens. Tokens are shown once at creation — store them somewhere safe. Use the token as your password when git prompts for credentials.

Creating repositories

Visit /new and pick an owner, a name, a default branch, and visibility. Everything else (description, README, license) is optional.

Pushing & pulling

Standard git over SSH or HTTPS:

git clone git@gitcritter.com:owner/repo.git
# or
git clone https://gitcritter.com/owner/repo.git

Push and pull as usual. The default branch is whatever you picked at repo creation.

Pull requests

Push a branch, then visit the repo's /pulls tab to open a pull request. Reviews can be left line-by-line. Merging supports a standard merge commit or a squash.

API

A small REST API lives under /api/v3. Authenticate with a personal access token using the Authorization: Bearer header. The shape covers the common repository, user, and pull request endpoints; not every field is mirrored.

Docs — GitCritter | GitCritter