Any remote you already push to - not just GitHub. A write here is a commit, so the history is an audit trail this app did not have to invent.
| Field | What goes there |
|---|---|
| repository url | https://host/org/reviews.git |
| branch | Defaults to main |
| path in the repository | Optional - a prefix, if drafts do not sit at the root |
| username / access token | For an https remote. Not needed for ssh, on the desktop app - see below |
| cors proxy | Browser only - see below |
On the desktop app, this drives the git already installed on the machine - it inherits whatever credential helper and ssh agent are already set up, so an ssh remote needs no token at all here.
A browser has no git of its own, so the same work happens in JavaScript against the smart-HTTP protocol - and no major git host sends the CORS headers a browser tab needs to speak that protocol directly. Reaching one from a browser needs a proxy you name, and the header carrying your token passes through that proxy too. Run it yourself, or use the desktop app instead, which needs none.
The same repository a GitHub repository would reach through the REST API, seen through different plumbing - one adapter over two transports, chosen once per session rather than two adapters that happen to agree. What it trades for that history: a real clone, and every listed file carries the blob id git already computed, rather than a timestamp and a size.