Skip to content

issue-tracker 0.1.3: sync after connecting through an existing connection - #249

Merged
michielbdejong merged 3 commits into
mainfrom
claude/issue-tracker-existing-connection
Oct 2, 2026
Merged

michielbdejong merged 3 commits into
mainfrom
claude/issue-tracker-existing-connection

Conversation

@michielbdejong

Copy link
Copy Markdown
Contributor

Picking "Use existing connection" in the host's consent bar resolves proxy.connect without a reload, but connect() only ran load(). Only main.ts's initial path listed repositories or ran the first sync, so the app stopped at an empty repository picker or at a board that never synced. Found in #196's user-testing work. It is the same bug #247 fixes in Notion.

  • Fix: the controller gets start(): load, then list repositories (picker) or sync (bound). view() and connect() both use it, so the two paths can't drift. Saved view prefs are applied on the first ready state.
  • Unit tests cover both cases; the fake store gains an existing option. With connect() reverted to load(), they fail.
  • E2e step 7: Disconnect GitHub in the app, then "Use existing connection" without a reload; the app syncs by itself. The repository-picker case is covered by unit tests only, because it would need a second install.
  • Release: app 0.1.3 is published to apps/issue-tracker/0.1.3/ui.js (137,359 bytes, within the existing 148 KiB limit). The catalog entry and usertest/catalog.mjs (usertest-5) are updated.

Checks: issue-tracker unit, typecheck and e2e lanes pass. Also: tooling tests 248/248, apps and ontology checks, certify, e2e tsc, oxlint (0 errors) and oxfmt. Not verified against live GitHub.

🤖 Generated with Claude Code

michielbdejong and others added 2 commits October 1, 2026 15:39
…tion

Picking "Use existing connection" in the host's consent bar resolves
proxy.connect with no reload, but connect() only ran load(): the app
stopped at an empty repository picker, or at a board that never synced.
Only main.ts's initial path listed repositories or ran the first sync.

The controller now has start(): load, then list repositories
(choose-repository) or sync (ready). view() and connect() both use it, so
the two paths cannot drift; main.ts applies the saved view prefs on the
first ready state instead. Unit tests cover both cases; the e2e adds a
step 7: Disconnect GitHub in the app, then connect again through the
existing connection, and the app syncs by itself with no reload.

App 0.1.3 (usertest-5). Found in the #196 user-testing work; same bug as
fixed in Notion on claude/notion-two-way (#247).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	usertest/catalog.mjs
@michielbdejong
michielbdejong merged commit 6dabc23 into main Oct 2, 2026
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant