Step 4 of #201. From the owner's first look at the build (2026-11-11): the app opens on a card that says "Connect to GitHub", and Gitea exists only in Add account. GitHub and Gitea are to be equal options throughout.
What
The Quick Sync card asks where the repositories are, with the same two options and labels as the wizard (GitHub, Gitea), and for Gitea the server address. The choice comes first on the card.
The title, the token box and the "How to create a token" link follow the place.
The card opens on the place and server that last worked (first run: GitHub). The address is kept in settings.json; a token never is.
A token is sent only to the place that is on the card when it is sent, and only once the address is complete (the address is taken when its box is left, not while it is typed). A token that was used with one place is emptied when another place is chosen.
"Save as account" carries the place over.
The offline UI fixture and the UI suite cover a Quick Sync connection to a Gitea server.
Then
Step 5: Settings holds a default token per forge (GitHub; Gitea with its server address). Step 6: wording in About, the Share invitation and the README.
Step 4 of #201. From the owner's first look at the build (2026-11-11): the app opens on a card that says "Connect to GitHub", and Gitea exists only in Add account. GitHub and Gitea are to be equal options throughout.
## What
- The Quick Sync card asks where the repositories are, with the same two options and labels as the wizard (**GitHub**, **Gitea**), and for Gitea the server address. The choice comes first on the card.
- The title, the token box and the "How to create a token" link follow the place.
- The card opens on the place and server that last worked (first run: GitHub). The address is kept in `settings.json`; a token never is.
- A token is sent only to the place that is on the card when it is sent, and only once the address is complete (the address is taken when its box is left, not while it is typed). A token that was used with one place is emptied when another place is chosen.
- "Save as account" carries the place over.
- The offline UI fixture and the UI suite cover a Quick Sync connection to a Gitea server.
## Then
Step 5: Settings holds a default token per forge (GitHub; Gitea with its server address). Step 6: wording in About, the Share invitation and the README.
Scope extended on 2026-11-11 after talking the start screen through with the owner ("do it"). The start screen is the thing the user most likely came to do, decided by what the app already knows:
State at start
Opens on
Already filled in
First run
Quick Sync card, with the place choice on top
Nothing
No accounts, a connection worked before
Quick Sync card
Place, server address, organization and target folder from last time; a token only from a saved default
Accounts exist, nothing recorded yet
The first account
Its repositories load on open
Accounts exist
The workspace that was open last (an account or Quick Sync); the first account if that one is gone
Same
One card on first run, no separate welcome step.
After the first successful load on Quick Sync, "Save as account" is offered as a clear prompt, not a line of caption text.
Quick Sync sends no token at startup by itself; it fills in and waits for Load. It never remembers a token.
Scope extended on 2026-11-11 after talking the start screen through with the owner ("do it"). The start screen is the thing the user most likely came to do, decided by what the app already knows:
| State at start | Opens on | Already filled in |
| --- | --- | --- |
| First run | Quick Sync card, with the place choice on top | Nothing |
| No accounts, a connection worked before | Quick Sync card | Place, server address, organization and target folder from last time; a token only from a saved default |
| Accounts exist, nothing recorded yet | The first account | Its repositories load on open |
| Accounts exist | The workspace that was open last (an account or Quick Sync); the first account if that one is gone | Same |
- One card on first run, no separate welcome step.
- After the first successful load on Quick Sync, "Save as account" is offered as a clear prompt, not a line of caption text.
- Quick Sync sends no token at startup by itself; it fills in and waits for Load. It never remembers a token.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Step 4 of #201. From the owner's first look at the build (2026-11-11): the app opens on a card that says "Connect to GitHub", and Gitea exists only in Add account. GitHub and Gitea are to be equal options throughout.
What
settings.json; a token never is.Then
Step 5: Settings holds a default token per forge (GitHub; Gitea with its server address). Step 6: wording in About, the Share invitation and the README.
Scope extended on 2026-11-11 after talking the start screen through with the owner ("do it"). The start screen is the thing the user most likely came to do, decided by what the app already knows: