Skip to content

chore(sync): merge pingdotgg/t3code main - #300

Merged
Yarden-zamir merged 9 commits into
mainfrom
fork-sync/2026-10-22-2306
Oct 22, 2026
Merged

Yarden-zamir merged 9 commits into
mainfrom
fork-sync/2026-10-22-2306

Conversation

@Yarden-zamir

Copy link
Copy Markdown
Owner

Fork Sync failed on merge conflicts: https://github.com/Yarden-zamir/t3code/actions/runs/39869393173. Issue: #286.

Conflicts

  • apps/server/src/orchestration-v2/pullRequestWatch.ts: upstream fix(server): wake PR watches when no checks report pingdotgg/t3code#23863 adds a required now parameter to evaluatePullRequestWatch. The fork adds an optional remarkFilter parameter (fork pull request watch remark filter). Kept both, with now first, because a required parameter must come before an optional one.
  • apps/server/src/orchestration-v2/PullRequestWatchReactor.ts: the reactor passes both now and the fork remarkFilter.
  • apps/server/src/orchestration-v2/pullRequestWatch.test.ts: kept both import lists. Upstream's test wrapper type expects now as the last parameter, so with the fork parameter after it the type became never. Replaced the wrapper with explicit parameters, here and in pullRequestWatch.forgejoComments.test.ts.
  • apps/server/src/ws.ts: upstream fix(server): preserve typed requirements as the RPC group grows pingdotgg/t3code#23813 registers the RPC handlers as two smaller groups to stay under a TypeScript limit. The fork registers its own RPCs in a separate layer and removes them from the core group (ServerWsRpcGroupCore). The two upstream groups are now built from the fork core group, so each handler is registered once.
  • pnpm-lock.yaml: upstream raises the Clerk Expo SDKs (chore(mobile): bump Clerk Expo SDKs to the new native client sync pingdotgg/t3code#23047). Took the fork lockfile and re-resolved it. It matches the upstream lockfile change, except for the supports-color peer version that the fork lockfile already resolves (10.2.2).

Upstream changes in fork areas

  • runtimeLayer.test.ts: two new upstream pull request watch tests did not provide server settings, which the fork watch needs for its remark filter. Commit 6bb3b99 adds ServerSettings.layerTest() to them, as in the fork's other watch tests.
  • Orchestrator.ts: upstream keeps checksAwaitedSince on an ended watch. The fork fork-thread source point code is unaffected.
  • CodexAdapterV2.ts: upstream wakes a Codex parent when a native child finishes. The fork thread credential in shell environment is unaffected.
  • apps/mobile/package.json, pnpm-workspace.yaml: Clerk version bump next to the fork font and speech dependencies. No conflict in behaviour.

Checks

  • vp run typecheck: 35 of 35 packages pass.
  • Pull request watch tests (pullRequestWatch.test.ts, pullRequestWatch.forgejoComments.test.ts, watch tests in runtimeLayer.test.ts): pass.
  • Fork test files: started on the build machine. Fork CI runs the full suites on this pull request.

wobsoriano and others added 9 commits October 22, 2026 14:08
…ngdotgg#23047)

Co-authored-by: Julius Marminge <julius0216@outlook.com>
Co-authored-by: Claude Haiku 5.5 <noreply@anthropic.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…otgg#23840)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…h git.cafe (pingdotgg#23887)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	apps/server/src/orchestration-v2/PullRequestWatchReactor.ts
#	apps/server/src/orchestration-v2/pullRequestWatch.test.ts
#	apps/server/src/orchestration-v2/pullRequestWatch.ts
#	apps/server/src/ws.ts
#	pnpm-lock.yaml
The fork pull request watch reads its remark filter from server settings. Upstream pingdotgg#23863 adds two watch tests without that service.
@Yarden-zamir
Yarden-zamir merged commit e8b1ead into main Oct 22, 2026
18 of 19 checks passed
@Yarden-zamir
Yarden-zamir deleted the fork-sync/2026-10-22-2306 branch October 22, 2026 23:31
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.

3 participants