KofTwentyTwo/gclo
2
0 Fork 0
Code Issues 28 Pull Requests 1 Actions Packages Projects Releases 22 Wiki Activity

The Add account wizard can add an account on a Gitea server #206

New Issue
Closed
opened 2026-11-11 07:17:51 +00:00 by james.maes · 0 comments
james.maes commented 2026-11-11 07:17:51 +00:00
Owner
Copy link
Copy source

Step 3 of #201, after #202 (listers) and #204 (accounts and the command line).

What

The desktop app's Add account wizard can add an account on a Gitea server.

  • Step 1 asks where the account lives: GitHub (default) or a Gitea server, with the server's address. The address is checked with the same rule as the command line (HTTPS only, no user name or password in it) and shown as it was normalized.
  • The token on step 2 is checked against the chosen place and nowhere else. A token that was typed for one place is not kept when the place is changed.
  • The default token is not offered for a Gitea server (it is a GitHub token).
  • An edit shows where the account lives and cannot change it.
  • Texts and links that name GitHub follow the account's forge (the connect card, the "How to create a token" link).
  • The offline UI fixture answers for a Gitea server as well, and the UI suite goes through the wizard with it.
  • README and ADR 0010.

Done when

  • A Gitea account can be added, loaded and synced from the app.
  • Tests pin: the token goes to the chosen place only; the choice is absent from an edit and from "Save as account" (a Quick Sync connection is a GitHub connection).
  • Gates pass, 100% line coverage.
Step 3 of #201, after #202 (listers) and #204 (accounts and the command line). ## What The desktop app's Add account wizard can add an account on a Gitea server. - Step 1 asks where the account lives: GitHub (default) or a Gitea server, with the server's address. The address is checked with the same rule as the command line (HTTPS only, no user name or password in it) and shown as it was normalized. - The token on step 2 is checked against the chosen place and nowhere else. A token that was typed for one place is not kept when the place is changed. - The default token is not offered for a Gitea server (it is a GitHub token). - An edit shows where the account lives and cannot change it. - Texts and links that name GitHub follow the account's forge (the connect card, the "How to create a token" link). - The offline UI fixture answers for a Gitea server as well, and the UI suite goes through the wizard with it. - README and ADR 0010. ## Done when - A Gitea account can be added, loaded and synced from the app. - Tests pin: the token goes to the chosen place only; the choice is absent from an edit and from "Save as account" (a Quick Sync connection is a GitHub connection). - Gates pass, 100% line coverage.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
.NET
Pull requests that update .NET code
 bug
Something isn't working
 deferred
Agreed follow-up, not scheduled
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 needs-owner
Blocked on an action only the owner can take
 priority
Owner-flagged: work this first
 quality
Standards, simplicity, enforcement
 question
Further information is requested
 refactor
Restructuring without behavior change
 release
Release pipeline / distribution
 wontfix
This will not be worked on
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#206