2026-11-05 - 2026-11-12
Overview
32 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
34 Issues closed from 1 user
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
#167 The window stops responding while a large account syncs, and nothing says that Sync all is running
Closed
#168 The repository table follows the sync by default, and the Sync all status is one aligned row
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
52 Issues created by 1 user
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
#179 A workspace has one activity state, and a run keeps the inputs it started with
Opened
#178 A repository follows a renamed default branch also under path recovery, and its new tree is validated before it is written
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
#187 An empty clone whose first commit has invalid paths can be resolved when the origin's branch has another name
Opened
#186 A new invalid path under a folder that was already renamed can be resolved
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
#194 The repository table: the cost of building a row, and pages that are rebuilt when switching accounts
Opened
#193 Very long branch names can exceed the path limit inside .git
Opened
#195 A detailed activity log
Opened
#196 README screenshots show the 1.1.1 window, and Share offers the invitation text to copy
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
5 Unresolved Conversations
Open
#56
Verify self-update on a dev-channel install with Velopack 1.2.161
Open
#7
Owner setup checklist: publishing secrets + dev mode
Open
#11
Development roadmap (tracking issue)
Open
#62
Standards compliance: make gclo conform to KofTwentyTwo/standards for the 1.0.1 release (epic)
Open
#66
Maintainer checklist: repository settings, rulesets, environments, exceptions, and process items for standards compliance