Skip to content

chore: register Discord and VS Code integration overlays - #81

Merged
patroza merged 1 commit into
fork/changesfrom
chore/register-client-overlays
Jul 26, 2026
Merged

chore: register Discord and VS Code integration overlays#81
patroza merged 1 commit into
fork/changesfrom
chore/register-client-overlays

Conversation

@patroza

@patroza patroza commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Summary

Once merged, the fork stack workflow rebases both overlays and composes them into fork/integration after desktop links (#10).

@patroza
patroza merged commit 3714834 into fork/changes Jul 26, 2026
@patroza
patroza deleted the chore/register-client-overlays branch July 26, 2026 08:29
patroza added a commit that referenced this pull request Aug 15, 2026
## Summary

The thread PR panel used the project's primary repository identity. On a
fork that prefers **upstream**, so `#410` was loaded as
`pingdotgg#410`.

That number exists only on the fork:

| Repo | #410 |
| --- | --- |
| `patroza/t3code` | open — docs(agents): drop obsolete fork stack
workflow |
| `pingdotgg/t3code` | GraphQL: could not resolve |

The agent on the left found the fork PR (`gh pr view 410` with `GH_REPO`
/ origin). The panel asked GitHub for the upstream number and showed
**Pull request not found**.

This is not the earlier App-install / wrapper issue. Ops #81 and product
#408 already landed; t3vm is minting public-read fallback tokens.

**Fix:** open the panel from the change-request URL (`patroza/t3code`),
and accept any of the checkout's remotes on the server so origin is
still this project.

## Test plan

- [x] `vp test run
apps/server/src/pullRequest/PullRequestService.test.ts
apps/web/src/components/pullRequest/pullRequestDetail.logic.test.ts`
- [ ] After deploy: open the `#410` thread panel and confirm it loads
`#410`
- [ ] Confirm an upstream PR on the same checkout still opens against
`pingdotgg/t3code`

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
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