A repository you already have, read and written through the API with a token that is yours. GitHub allows the cross-origin request a browser tab needs, so nothing proxies it.
| Field | What goes there |
|---|---|
| owner | The account or organisation the repository belongs to |
| repository | Its name |
| branch | Defaults to main |
| path in the repository | Optional - a prefix, if drafts do not sit at the root |
| access token | Fine grained, scoped to this repository only: Contents, read and write |
Anywhere. api.github.com allows cross-origin requests carrying an Authorization header, which is the one thing a browser tab needs and no other host in this list grants for free - see a git repository, which needs a proxy for exactly the request this does not.
The token is kept in this browser and sent as a bearer header, straight to GitHub. Nothing proxies it, and no credential exists anywhere but the machine you are sitting at.
What is traded against a git repository, the other GitHub-shaped option: no commit graph in a tab, so this reads and writes files one at a time through five REST endpoints rather than cloning. The write still lands as a commit on GitHub's side, so the audit trail survives either way - this just gets there without a local git of its own.