Step 3 of Gitea support (#201): the desktop app adds, loads and syncs an account on a Gitea server. - Step 1 of the wizard asks, for a new account, where the repositories are: GitHub (the default) or a Gitea server and its address. The address is checked by the rule the command line uses and shown as it was normalized, which is the address the token goes to. - The wizard holds the lister of one place at a time. The shell gives it a lister per place, step 1 takes the one of the chosen place, and step 2 has no other to send the token to. A wizard that was given one lister (an edit, a Quick Sync connection saved as an account) offers no choice and says where the account is. - What was entered for one place is not carried to another: when step 1 is left with another place than before, the typed token, the organization and the organization list are emptied. The default token is a GitHub token and is neither offered nor preselected for a Gitea server. - Texts that named GitHub follow the place: the token box, the page a token is made on, the note of step 2, and the connect card of an account's page. - The offline UI fixture answers for a Gitea server with an organization of its own, and the UI suite walks the wizard for one. The wizard's listers are wrapped by the fixture like a workspace's. - README, ADR 0010, threat model T16. Included, from the reviews of this pull request: - fix(app): the wizard names the whole server address where the token is asked for, takes a place only with its lister, and does not move while a token is checked - fix(app): the wizard's choice of place reads GitHub and Gitea Closes #206 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>
48 KiB
1233x928px
48 KiB
1233x928px