2025-11-14 - 2026-11-14
Overview
24 Releases published by 2 users
Published
v1.1.0
gclo 1.1.0
Published
v1.1.0-beta.1
gclo 1.1.0-beta.1
Published
v1.0.2-beta.3
gclo 1.0.2-beta.3
Published
v1.0.2-beta.2
Published
v1.0.2-beta.1
gclo 1.0.2-beta.1
Published
v1.0.1
gclo 1.0.1
Published
v1.0.1-beta.3
gclo 1.0.1-beta.3
Published
v1.0.1-beta.2
Published
v1.0.1-beta.1
gclo 1.0.1-beta.1
Published
v1.0.0
gclo 1.0.0
Published
v0.1.0-beta.15
gclo 0.1.0-beta.15
Published
v0.1.0-beta.14
gclo 0.1.0-beta.14
Published
v0.1.0-beta.13
gclo 0.1.0-beta.13
Published
v0.1.0-beta.12
gclo 0.1.0-beta.12
Published
v0.1.0-beta.11
gclo 0.1.0-beta.11
Published
v0.1.0-beta.10
gclo 0.1.0-beta.10
Published
v0.1.0-beta.9
gclo 0.1.0-beta.9
Published
v0.1.0-beta.8
gclo 0.1.0-beta.8
Published
v0.1.0-beta.7
gclo 0.1.0-beta.7
Published
v0.1.0-beta.6
gclo 0.1.0-beta.6
Published
v0.1.0-beta.5
gclo 0.1.0-beta.5
Published
v0.1.0-beta.4
gclo 0.1.0-beta.4
Published
v0.1.0-beta.3
gclo 0.1.0-beta.3
Published
v0.1.0-beta.2
gclo 0.1.0-beta.2
84 Pull requests merged by 2 users
Merged
#217 feat(app): gclo opens one window per data folder, and a second start brings the open one to the front
Merged
#220 ci(gitea): build, test, coverage and format on the Windows host runner
Merged
#219 docs(release): the documents name 1.2.0 as the release that moves updates to git.kof22.com
Merged
#215 feat(app): Settings holds a default token per forge, and a default token is used only for the place it was saved for
Merged
#214 feat(app): the next version is 1.2.0, and gclo describes itself as for GitHub and Gitea alike
Merged
#210 feat(app): Quick Sync connects to GitHub or Gitea, sends a token only when asked, and the app opens where it was left
Merged
#207 feat(app): the Add account wizard asks where the repositories are, and can add an account on a Gitea server
Merged
#205 feat(accounts): an account names its forge and server, and the command line takes --forge and --server
Merged
#203 feat(engine): a forge-neutral failure type and listers for Gitea servers
Merged
#198 fix(engine): a folder's own configuration names no proxy for the fetch, and git's own folder name is not a repository name
Merged
#199 docs(release): the documents say what 1.1.1 does, and the package manifests verify the file they name
Merged
#185 fix(app): an account's page takes no token it would ignore, and Sync all does not call an unsynced account synced
Merged
#171 feat(update): updates and release downloads come from git.kof22.com
Merged
#175 fix(clone): clones that were empty, cut off, or still ending are handled safely by the next sync
Merged
#177 docs(agents): CLAUDE.md covers the build traps, the test layout, and the architecture as it is now
Merged
#173 fix(wizard): an empty token box asks for a token instead of showing a raw error
Merged
#169 fix(app): the window stays responsive during a sync, Sync all says where it stands, and the table follows the sync
Merged
#166 chore(links): point the project's links at its Gitea home
Merged
#164 feat(app): Help > Share gclo by email, a ready-to-send invitation with download links
Merged
#162 test: the suites write nothing outside their own folders and send nothing anywhere
Merged
#158 fix(app): a saved token is read when it is used, not once when a workspace opens
Merged
#148 fix(recovery): never discard local work, and deliver the commits it reports
Merged
#160 fix(cli): exit codes, option handling and Ctrl+C for accounts and dry runs; the log follows GCLO_DATA_DIR
Merged
#156 fix(accounts): accounts.json is safe across gclo processes; an unreadable file is not a corrupt one
Merged
#146 fix(app): scope the UI test fixture to its token, never in an installed build
Merged
#154 fix(github): classify access, network and server failures; cancel a listing promptly
Merged
#152 fix(engine): small correctness fixes found in the 1.1.1 review
Merged
#150 fix(recovery): plans are checked by where paths end up; suggestions are valid
Merged
#144 fix(log): show control characters from repository content as visible text
Merged
#142 fix(recovery): keep every write and delete inside the working tree
Merged
#140 fix(sync): pull only a clone of the listed repository, over the listed URL
Merged
#138 build: pin the single-file analyzer package so lock files survive SDK patches
Merged
#134 docs: say Chocolatey and winget are not available yet
Merged
#133 build(chocolatey): address the moderation validator's guideline notes
Merged
#130 ci(release): open the packaging manifests PR before the Chocolatey push
Merged
#123 build(packaging): point the Scoop and Chocolatey manifests at v1.1.0
Merged
#117 ci(release): verify the CLI zip under the edition's app id
Merged
#115 feat(release): pack the dev channel as its own app so it installs beside stable
Merged
#113 feat(help): Submit an issue and Community support links
Merged
#112 feat(settings): show a saved default token as a mask and say what Save will do
Merged
#111 feat(wizard): offer the default token when adding or editing an account
Merged
#110 feat(accounts): reference the default token instead of copying it
Merged
#100 ci(release): run verify-signatures in the release environment
Merged
#98 ci(release): re-pin the shared Velopack workflow to the signing fix
Merged
#96 feat(release): Authenticode-sign releases with Azure Artifact Signing over OIDC
Merged
#94 fix: keep per-user data out of the Velopack install root
Merged
#90 ci: retry PSScriptAnalyzer per file when it throws
Merged
#88 fix(release): keep build and publish on one resource configuration; smoke test what ships
Merged
#86 ci(release): open the packaging PR with a release GitHub App token
Merged
#84 build(packaging): point the Scoop and Chocolatey manifests at v1.0.1
Merged
#82 ci(release): sign off the generated packaging commit
Merged
#79 fix(build): enable ReadyToRun and trimming only when publishing
Merged
#77 ci: release through the standards' shared Velopack workflow; publishers fail instead of skip
Merged
#75 docs: name the CI gates as the required checks report them
Merged
#73 chore: ignore the layout commit in git blame
Merged
#71 ci: retire the gates the standards' reusable workflows superseded
Merged
#70 style: adopt the Kingsrook C# layout and the standard .NET quality gate
Merged
#69 docs: align governance files, ADRs, and the threat model with the standards
Merged
#68 ci: adopt the standards' pull-request, security, CodeQL and Scorecard gates
Merged
#61 Isolate the Credential Manager vault per data directory (#60)
Merged
#59 Package managers, Clone-in-WSL recovery, WinUI.TableView table (#9, #8, #33)
Merged
#58 Known-issues sweep: verified review findings (#30, #31, #32), update progress (#39), full action logging (#40)
Merged
#51 Post-1.0 hardening: deps, release/CodeQL gates, engine containment and clone recovery, account consistency, NuGet update workflow
Merged
#42 Docs current for v1.0.0 + post-1.0 dev version baseline
Merged
#41 README: application screenshots
Merged
#38 Fix: publish brand assets so installed builds show the icon (beta.15)
Merged
#37 Brand identity: true-vector icon, standard Windows icon set, window + splash + About branding (beta.14)
Merged
#36 100% enforced coverage (Engine/ViewModels/CLI) + Sync All sidebar status (beta.13)
Merged
#35 Account-org hardening, settings expansion, live log window, tooltips (beta.12)
Merged
#34 Toolbar clipping fix, header filters, review fixes (beta.11)
Merged
#29 Dialog-collision crash fix, FlaUI e2e suite, branded splash (beta.10)
Merged
#28 Phase 4: account wizard, edit/delete, Sync All
Merged
#27 Phase 3: workspace redesign
Merged
#26 Phase 2: NavigationView shell with per-account workspaces
Merged
#25 Phase 1: accounts foundation (model, vault, store, CLI)
Merged
#24 Build identity: version + git hash synced to releases
Merged
#23 Phase 0: P1 accessibility/theming wave (#22)
Merged
#18 Audit: analyzer enforcement + 28 verified findings fixed (#5)
Merged
#14 Bump Microsoft.NET.Test.Sdk from 17.14.1 to 18.7.0
Merged
#12 Bump the nuget-minor-patch group with 1 update
Merged
#13 Bump coverlet.collector from 6.0.4 to 10.0.1
Merged
#17 Path recovery: rename/skip Windows-invalid paths (#2)
Merged
#15 Fix release pipeline for immutable releases
Merged
#1 Productionize: tests, CLI, CI/CD, self-update
1 Pull request proposed by 1 user
Proposed
#136 ci: Bump the actions group across 1 directory with 7 updates
85 Issues closed from 2 users
Closed
#216 Settings saved in one window are put back by the Settings dialog of another window
Closed
#218 Documents still say 1.1.1; the release is 1.2.0
Closed
#201 Gitea organizations and accounts beside GitHub
Closed
#212 Settings holds a default token per forge: GitHub, and a Gitea server with its token
Closed
#211 The next version is 1.2.0, and what the app says about itself names GitHub and Gitea alike
Closed
#209 Quick Sync can connect to a Gitea server: GitHub and Gitea are equal on the start page
Closed
#213 The button at the top of the navigation pane does nothing, and stands there alone
Closed
#206 The Add account wizard can add an account on a Gitea server
Closed
#204 Accounts and command line: a forge and a server per account
Closed
#202 Engine: a forge-neutral failure type and the Gitea listers
Closed
#184 A folder's own configuration names no proxy for the fetch, and git's own folder name is not a repository name
Closed
#183 Documents and release tooling match 1.1.1: stale statements, and package manifests that verify the file they name
Closed
#182 An account's page ignores a typed token, and Sync all reports accounts it could not sync as a success
Closed
#170 Updates and release downloads come from git.kof22.com
Closed
#174 Clones that were empty, cut off, or still ending are handled safely by the next sync
Closed
#176 CLAUDE.md: build traps, test layout, and the architecture as it is now
Closed
#172 The account wizard shows a raw error when the token box is empty
Closed
#168 The repository table follows the sync by default, and the Sync all status is one aligned row
Closed
#167 The window stops responding while a large account syncs, and nothing says that Sync all is running
Closed
#165 chore(links): point the project's links at its Gitea home
Closed
#163 feat(app): Help > Share gclo by email, a ready-to-send invitation with download links
Closed
#161 test: the suites write nothing outside their own folders and send nothing anywhere
Closed
#157 fix(app): a saved token is read when it is used, not once when a workspace opens
Closed
#147 Path recovery: never discard local work, and deliver the commits it reports
Closed
#159 fix(cli): exit codes, option handling and Ctrl+C for the accounts and dry-run commands; the log follows GCLO_DATA_DIR
Closed
#155 fix(accounts): accounts.json is safe across gclo processes; an unreadable file is not a corrupt one
Closed
#145 UI test fixture: only the fixture token is affected, and never in an installed build
Closed
#153 fix(github): classify access, network and server failures; cancel a listing promptly; no progress after a final state
Closed
#151 fix(engine): small correctness fixes (drive-root target, concurrency bounds, process cleanup, activity log)
Closed
#149 Path recovery plans: validate where paths end up, and make every suggested name valid
Closed
#143 Log and CLI text: show control characters from repository content as visible escapes
Closed
#141 Path recovery: keep every write and delete inside the working tree
Closed
#139 Sync only the listed repository: verify an existing folder's origin and tie git credentials to the listed host
Closed
#137 build: SDK patch drift breaks locked restore (NU1004); refresh the lock files
Closed
#131 Chocolatey nuspec: address the moderation validator's guideline notes
Closed
#102 Add account: use the default token when one is saved, with the option to enter a different one
Closed
#129 release: open the packaging manifests PR even when the Chocolatey push fails
Closed
#67 Release v1.0.1
Closed
#116 release: verify-signatures looks for the CLI zip under the stable name on a prerelease
Closed
#114 Dev channel installs as a separate app (gclo-dev) so stable and dev can coexist
Closed
#108 Help menu: Submit an issue and Community support links
Closed
#101 Settings: a saved default token shows as a masked value, not an empty box
Closed
#105 Add account wizard offers the default token; pane tag; Sync All names Settings (plan step 2)
Closed
#104 Accounts can reference the default token: model, resolver, store and CLI (plan step 1)
Closed
#99 release: verify-signatures job cannot read TRUSTED_SIGNING_SUBJECT (not in the release environment)
Closed
#97 release: re-pin the shared Velopack workflow to the signing fix (standards#29)
Closed
#57 Sign release binaries (Setup, packages, CLI) — needs a signing identity from the owner
Closed
#91 Setup.exe over an existing install deletes accounts.json and settings.json (data lives in the Velopack install root)
Closed
#89 ci: PSScriptAnalyzer 1.25.0 still crashes intermittently (NullReference) in per-file mode
Closed
#87 v1.0.1 crashes at startup (0xc000027b): published gclo.pri lacks the WinUI resources
Closed
#85 release: packaging PR commit is unsigned, blocked by protect-main's signed-commits rule
Closed
#81 release: packaging PR commit has no DCO sign-off, so pr / dco fails
Closed
#78 Release build fails on a clean runner: ReadyToRun pack is not restored (NETSDK1094)
Closed
#76 Release through the standards' shared Velopack workflow; publish steps fail instead of skipping
Closed
#54 Make the UI end-to-end suite a required check for main and releases once proven stable
Closed
#74 CONTRIBUTING lists the CI gates under the wrong check names
Closed
#72 Ignore the Kingsrook layout commit in git blame
Closed
#65 style: adopt the Kingsrook C# layout, standard .editorconfig and Directory.Build.props, central package management
Closed
#64 docs: standards-aligned README, SECURITY, CONTRIBUTING, templates, ADRs, threat model, CLAUDE.md
Closed
#63 ci: adopt the standards' pull-request, security, CodeQL and Scorecard gates and harden the release pipeline
Closed
#60 UI tests: Credential Manager vault is not isolated by GCLO_DATA_DIR (the suite sees the developer's saved default token)
Closed
#55 Rehearse the gated release chain with v1.0.1-beta.1
Closed
#8 Clone-in-WSL recovery option for Windows-invalid paths
Closed
#33 Adopt WinUI.TableView for the repo table (wait for its accessibility release)
Closed
#9 Chocolatey / Scoop manifests
Closed
#32 Full app review (unverified, 2/2): security, CLI, release-engineering findings
Closed
#31 Full app review (unverified, 1/2): engine, XAML, test-quality findings
Closed
#39 Visual indicator while checking for / applying updates
Closed
#40 Log 100% of user/app actions to the activity log
Closed
#30 Full app review (verified): 17 UX + performance findings
Closed
#43 Make account metadata and token-vault updates recoverable
Closed
#46 Detect and recover incomplete working trees after failed clones
Closed
#53 Dependency review fails on file-licensed packages (LibGit2Sharp, WindowsAppSDK, SDK BuildTools)
Closed
#47 Validate repository names and contain sync target paths
Closed
#52 NuGet dependency updates never arrive: Dependabot cannot evaluate the WinUI target framework
Closed
#45 Run CodeQL for dev pushes and pull requests
Closed
#44 Enforce full release gates and require tags from main
Closed
#6 First release: prove the pipeline end-to-end (beta then stable)
Closed
#10 README screenshot
Closed
#22 UI/UX review: 22 adversarially-verified findings (accessibility, theming, workflow, microcopy)
Closed
#16 Accounts mode: multi-account setup with secure token storage
Closed
#5 Best-practices/KISS audit + repo enforcement
Closed
#4 UX overhaul: selectable repo table, per-row progress, activity log, retry, path preview
Closed
#3 Extract gclo.ViewModels library — no business logic in the UI project
Closed
#2 Clones fail on Windows-invalid paths (chars, reserved names, too-long) that are fine on Linux
113 Issues created by 2 users
Opened
#2 Clones fail on Windows-invalid paths (chars, reserved names, too-long) that are fine on Linux
Opened
#3 Extract gclo.ViewModels library — no business logic in the UI project
Opened
#4 UX overhaul: selectable repo table, per-row progress, activity log, retry, path preview
Opened
#5 Best-practices/KISS audit + repo enforcement
Opened
#6 First release: prove the pipeline end-to-end (beta then stable)
Opened
#7 Owner setup checklist: publishing secrets + dev mode
Opened
#8 Clone-in-WSL recovery option for Windows-invalid paths
Opened
#9 Chocolatey / Scoop manifests
Opened
#10 README screenshot
Opened
#11 Development roadmap (tracking issue)
Opened
#16 Accounts mode: multi-account setup with secure token storage
Opened
#22 UI/UX review: 22 adversarially-verified findings (accessibility, theming, workflow, microcopy)
Opened
#30 Full app review (verified): 17 UX + performance findings
Opened
#31 Full app review (unverified, 1/2): engine, XAML, test-quality findings
Opened
#32 Full app review (unverified, 2/2): security, CLI, release-engineering findings
Opened
#33 Adopt WinUI.TableView for the repo table (wait for its accessibility release)
Opened
#39 Visual indicator while checking for / applying updates
Opened
#40 Log 100% of user/app actions to the activity log
Opened
#43 Make account metadata and token-vault updates recoverable
Opened
#44 Enforce full release gates and require tags from main
Opened
#47 Validate repository names and contain sync target paths
Opened
#46 Detect and recover incomplete working trees after failed clones
Opened
#45 Run CodeQL for dev pushes and pull requests
Opened
#52 NuGet dependency updates never arrive: Dependabot cannot evaluate the WinUI target framework
Opened
#53 Dependency review fails on file-licensed packages (LibGit2Sharp, WindowsAppSDK, SDK BuildTools)
Opened
#54 Make the UI end-to-end suite a required check for main and releases once proven stable
Opened
#55 Rehearse the gated release chain with v1.0.1-beta.1
Opened
#56 Verify self-update on a dev-channel install with Velopack 1.2.161
Opened
#57 Sign release binaries (Setup, packages, CLI) — needs a signing identity from the owner
Opened
#60 UI tests: Credential Manager vault is not isolated by GCLO_DATA_DIR (the suite sees the developer's saved default token)
Opened
#62 Standards compliance: make gclo conform to KofTwentyTwo/standards for the 1.0.1 release (epic)
Opened
#63 ci: adopt the standards' pull-request, security, CodeQL and Scorecard gates and harden the release pipeline
Opened
#64 docs: standards-aligned README, SECURITY, CONTRIBUTING, templates, ADRs, threat model, CLAUDE.md
Opened
#65 style: adopt the Kingsrook C# layout, standard .editorconfig and Directory.Build.props, central package management
Opened
#66 Maintainer checklist: repository settings, rulesets, environments, exceptions, and process items for standards compliance
Opened
#67 Release v1.0.1
Opened
#72 Ignore the Kingsrook layout commit in git blame
Opened
#74 CONTRIBUTING lists the CI gates under the wrong check names
Opened
#76 Release through the standards' shared Velopack workflow; publish steps fail instead of skipping
Opened
#78 Release build fails on a clean runner: ReadyToRun pack is not restored (NETSDK1094)
Opened
#81 release: packaging PR commit has no DCO sign-off, so pr / dco fails
Opened
#85 release: packaging PR commit is unsigned, blocked by protect-main's signed-commits rule
Opened
#87 v1.0.1 crashes at startup (0xc000027b): published gclo.pri lacks the WinUI resources
Opened
#89 ci: PSScriptAnalyzer 1.25.0 still crashes intermittently (NullReference) in per-file mode
Opened
#91 Setup.exe over an existing install deletes accounts.json and settings.json (data lives in the Velopack install root)
Opened
#97 release: re-pin the shared Velopack workflow to the signing fix (standards#29)
Opened
#99 release: verify-signatures job cannot read TRUSTED_SIGNING_SUBJECT (not in the release environment)
Opened
#101 Settings: a saved default token shows as a masked value, not an empty box
Opened
#102 Add account: use the default token when one is saved, with the option to enter a different one
Opened
#104 Accounts can reference the default token: model, resolver, store and CLI (plan step 1)
Opened
#105 Add account wizard offers the default token; pane tag; Sync All names Settings (plan step 2)
Opened
#108 Help menu: Submit an issue and Community support links
Opened
#114 Dev channel installs as a separate app (gclo-dev) so stable and dev can coexist
Opened
#116 release: verify-signatures looks for the CLI zip under the stable name on a prerelease
Opened
#118 Repo list filter tabs show how many repositories match (All (73), Active (2), Failed (1), Pending (70))
Opened
#119 Mark a repository as ignored so a known-bad repo stops failing every sync
Opened
#120 Settings: a default location for all accounts so the target folder need not be chosen per account
Opened
#121 Navigation pane: the hamburger icon is the wrong affordance for expand/collapse
Opened
#122 Repo list follows sync activity: scroll to the repository currently being synced
Opened
#129 release: open the packaging manifests PR even when the Chocolatey push fails
Opened
#131 Chocolatey nuspec: address the moderation validator's guideline notes
Opened
#137 build: SDK patch drift breaks locked restore (NU1004); refresh the lock files
Opened
#139 Sync only the listed repository: verify an existing folder's origin and tie git credentials to the listed host
Opened
#141 Path recovery: keep every write and delete inside the working tree
Opened
#143 Log and CLI text: show control characters from repository content as visible escapes
Opened
#145 UI test fixture: only the fixture token is affected, and never in an installed build
Opened
#147 Path recovery: never discard local work, and deliver the commits it reports
Opened
#149 Path recovery plans: validate where paths end up, and make every suggested name valid
Opened
#151 fix(engine): small correctness fixes (drive-root target, concurrency bounds, process cleanup, activity log)
Opened
#153 fix(github): classify access, network and server failures; cancel a listing promptly; no progress after a final state
Opened
#155 fix(accounts): accounts.json is safe across gclo processes; an unreadable file is not a corrupt one
Opened
#157 fix(app): a saved token is read when it is used, not once when a workspace opens
Opened
#159 fix(cli): exit codes, option handling and Ctrl+C for the accounts and dry-run commands; the log follows GCLO_DATA_DIR
Opened
#161 test: the suites write nothing outside their own folders and send nothing anywhere
Opened
#163 feat(app): Help > Share gclo by email, a ready-to-send invitation with download links
Opened
#165 chore(links): point the project's links at its Gitea home
Opened
#167 The window stops responding while a large account syncs, and nothing says that Sync all is running
Opened
#168 The repository table follows the sync by default, and the Sync all status is one aligned row
Opened
#170 Updates and release downloads come from git.kof22.com
Opened
#172 The account wizard shows a raw error when the token box is empty
Opened
#174 Clones that were empty, cut off, or still ending are handled safely by the next sync
Opened
#176 CLAUDE.md: build traps, test layout, and the architecture as it is now
Opened
#178 A repository follows a renamed default branch also under path recovery, and its new tree is validated before it is written
Opened
#179 A workspace has one activity state, and a run keeps the inputs it started with
Opened
#180 Sync all follows accounts that are edited or deleted while it runs
Opened
#181 Shell: lifetime, dialogs, navigation pane, log window, and accessibility items from the review
Opened
#182 An account's page ignores a typed token, and Sync all reports accounts it could not sync as a success
Opened
#183 Documents and release tooling match 1.1.1: stale statements, and package manifests that verify the file they name
Opened
#184 A folder's own configuration names no proxy for the fetch, and git's own folder name is not a repository name
Opened
#186 A new invalid path under a folder that was already renamed can be resolved
Opened
#187 An empty clone whose first commit has invalid paths can be resolved when the origin's branch has another name
Opened
#188 The state of an unfinished clone is one versioned record, written before the fetch
Opened
#190 Tests that depend on the machine say so, and fail on CI when they cannot run
Opened
#189 The updater checks something the release server cannot change
Opened
#192 Polish from the design review: messages, names, accessibility of the Resolve dialog, CLI help
Opened
#191 Decisions that are not written down: the move to Gitea, the state kept in .git, the accounts file lock
Opened
#193 Very long branch names can exceed the path limit inside .git
Opened
#194 The repository table: the cost of building a row, and pages that are rebuilt when switching accounts
Opened
#196 README screenshots show the 1.1.1 window, and Share offers the invitation text to copy
Opened
#195 A detailed activity log
Opened
#197 The release pipeline runs where the project lives
Opened
#200 Release v1.2.0
Opened
#201 Gitea organizations and accounts beside GitHub
Opened
#202 Engine: a forge-neutral failure type and the Gitea listers
Opened
#204 Accounts and command line: a forge and a server per account
Opened
#206 The Add account wizard can add an account on a Gitea server
Opened
#208 The command line cannot end a clash of two account names by itself
Opened
#209 Quick Sync can connect to a Gitea server: GitHub and Gitea are equal on the start page
Opened
#211 The next version is 1.2.0, and what the app says about itself names GitHub and Gitea alike
Opened
#212 Settings holds a default token per forge: GitHub, and a Gitea server with its token
Opened
#213 The button at the top of the navigation pane does nothing, and stands there alone
Opened
#216 Settings saved in one window are put back by the Settings dialog of another window
Opened
#218 Documents still say 1.1.1; the release is 1.2.0