Quickstart

Owner setup

Public onboarding is not open yet. This guide explains the existing owner flow so you can recognise each step when it becomes available.

Sign in with GitHub

GitHub supplies identity only. Gitpin does not request access to your GitHub repositories. A new owner explicitly accepts the current Terms; a returning owner does not need to repeat signup acceptance. One owner belongs to one organisation.

Create a repository

Choose a name. If a card is needed, the console opens Stripe's embedded setup form. Stripe handles payment details. Saving a card is not a repository creation confirmation and is not proof that an invoice was paid.

The console retains the original creation request and idempotency key after an interrupted response. Resume that request. Do not create another repository while the first result is uncertain.

Wait for readiness

Verification, allocation and provisioning are separate states. The repository is usable only when its server lifecycle says ready. Leaving setup pauses your browser flow; it does not delete or cancel a repository.

Issue a scoped key

Choose a repository, capabilities and expiry. The secret is shown once. Install it through your agent's trusted runtime or Git credential helper. Do not send it through chat or put it into a Git URL. See keys and scopes.

A pending setup URL identifies a request; it grants no authority. Sign in as the request's owner. Wrong-owner and unknown requests share a safe unavailable response. The agent continues retrying its original creation request while owner setup is pending.