# Your repository access

> How a purchase turns into read access to the private ZeroDirs repository — connecting a GitHub account, accepting the invitation, expired invitations, changing the account, and what a refund does.

You are reading one page of the ZeroDirs documentation. ZeroDirs is an Astro + Cloudflare Workers starter for directory sites: every page is rendered to static HTML at build time, the site ships no client JavaScript outside `/search/`, and one file — `site.config.ts` — carries roughly 80% of the customisation.

Two things to hold on to before you act on anything below:

- `site.config.ts` is validated by a zod schema with ten cross-field rules. After any edit to it, run `pnpm check:config`; every problem is reported as `site.config.ts › <path>: <message>` and the whole file is checked at once.
- The repository ships its own `AGENTS.md` with eighteen hard rules, and a machine-checked test suite behind them. If you are working inside a ZeroDirs project, read that file first — it overrides anything general you infer from this page.

Source: https://zerodirs.com/docs/start/repository-access/

---

A purchase gives **one GitHub account** read access to `zerodirs/zerodirs`, the private
repository the starter lives in. You choose the account yourself, on your access page, by
signing in to GitHub once; nobody at ZeroDirs types your username anywhere. The account is
bound to the order once — moving it later is one email.

## Your access page

Paying sends you straight to it, and the receipt email carries the same link, as does every
later email about the order — there is nothing to save. The page reads the state of your order
every time it loads, so what it shows is always current.

## Getting in

1. On your access page, press **Connect GitHub**.

   GitHub asks you to sign in (if you are not already) and to authorise the ZeroDirs app. The
   app asks for no permissions: ZeroDirs learns the account's public id and username, nothing
   else, and the sign-in token is used once and not kept.

2. The repository invitation is sent the moment you are back, to the account you just
   connected. The page says `Invitation sent to @you`, and an email confirms it.

3. Press **Accept on GitHub**, signed in as that account. GitHub lists the invitation at
   `https://github.com/zerodirs/zerodirs/invitations`; it also emails the invitation to that
   account's **primary email address**, which may not be the address you paid with.

4. Reload your access page after accepting. It shows the clone command:

   ```sh title="Terminal"
   git clone git@github.com:zerodirs/zerodirs.git my-directory
   ```

   From here the [Quickstart](https://zerodirs.com/docs/start/quickstart/) takes over. Updates are a `git pull`
   ([Updates](https://zerodirs.com/docs/about/updates/)).

> **Signed in as the wrong account?**
>
> GitHub sends the invitation to the account you connected, not the one you happen to be signed
> in as when you open the link. If GitHub shows no invitation, check which account is signed in.
> If you connected an account you did not mean to, see [Changing the account](#changing-the-account).

## The invitation expired, or you cannot find it

A GitHub repository invitation lasts **seven days**. If it expires, your access page offers
**Send a new invitation**; the old one is withdrawn and a fresh one starts the seven days
again. An expired invitation is also re-sent once automatically, within the hour, and you get
an email when it is.

A declined invitation counts as gone too: the page offers a new one in the same way.

## Changing the account

One GitHub account is bound to a purchase, and the access page connects it once. To move the
access to a different GitHub account — a new account, a work account, a colleague who takes
over — write to `hi@zerodirs.com` from the address you paid with, naming the order reference
shown on your access page. The previous account is removed and your access page goes back to
**Connect GitHub**, ready for the new one; connecting a second account without asking first is
refused with the same instruction.

## After a refund or a chargeback

Repository access is revoked automatically when a refund is issued, and likewise when a
chargeback is opened. Your access page then says *Access removed*, with the date, and you get
one email saying so. The licence ends with the access ([Terms](https://zerodirs.com/legal/terms/)).

## Lost the link?

Search your inbox for **Your ZeroDirs order**; the receipt links to your access page, and so
does every later email about the order. If none of them can be found, write to
`hi@zerodirs.com` from the address you paid with.

## A team

The licence covers one person or one company, and one GitHub account holds the repository
access. For a company where several people need to pull from the repository, write to
`hi@zerodirs.com` with the order reference from your access page.

## What is stored

Your email address, the Stripe order reference, the amount paid, and — once you connect it —
the id and username of the GitHub account and the state of its invitation. The full list is
on the [privacy page](https://zerodirs.com/legal/privacy/).

## Related

- [Quickstart](https://zerodirs.com/docs/start/quickstart/) — From the clone to the demo directory running on your machine.
- [Updates](https://zerodirs.com/docs/about/updates/) — What a release touches, and how to pull one.
- [Licence](https://zerodirs.com/docs/about/licence/) — The LICENSE file in plain words.
- [FAQ](https://zerodirs.com/docs/about/faq/) — What evaluators and first-week buyers ask.
