镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Associate conversation PRs and show status in the GitHub plugin - #3250

Draft
kazemek21 wants to merge 3 commits into
mainfrom
kylez_NEXUS-4453_solo_pr_status
Draft

kazemek21 wants to merge 3 commits into
mainfrom
kylez_NEXUS-4453_solo_pr_status

Conversation

@kazemek21

@kazemek21 kazemek21 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

TL;DR

Keep PR associations and status indicators inside the optional GitHub plugin, without extending core messaging. Personal associations work for Team, DM and Solo conversations, including read-only public channels, without publishing or changing membership or shared metadata.

After creating a conversation's own PR, an agent can explicitly call github_announce_pr with its URL and head branch. The plugin verifies signed-in GitHub authorship and branch before associating it; incidental links are never scanned or adopted.

Details

  • Show for me / Hide for me and github_link_pr manage a device-local overlay scoped to person, community and conversation. Cross-window storage locks preserve manual replacement/unlink against delayed automatic verification.
  • Existing shared Solo links remain a fallback. Explicit shared actions retain the original creator/writable-Solo boundary; personal choices do not grant shared-write access or sync to other devices.
  • Reuse public plugin tools/sidebar contributions, the native row/menu, shared GitHub state, Tooltip, Tabler icons and semantic tokens. No core API, separate poller, shell interception or merge action.
  • Show independent lifecycle, checks, review, discussion, conflict and readiness signals. Failed, stale, public-only or unsettled data cannot look ready. Readiness is display information, not permission to merge.

Verification

The corrected plugin-only snapshot is 5e97031dba146256cde5944a4616e94641408f0f. Isolated Blox tests, typecheck, Chromium/WebKit journeys and fresh independent Claude/Codex review are in progress; this PR remains draft. Previous-snapshot results do not establish corrected-snapshot validation.

Three browser scenarios were added; none removed. Two actual-app journeys cover native Solo and read-only Team wiring, persistence, keyboard/menu behavior and non-overlapping targets at wide/light and narrow/dark doubled-text sizes. A small rendering fixture covers approved status and failed-read readiness removal. Status/association matrices remain in unit tests. The earlier Solo journey exposed native menu starvation at narrow width; the plugin wrapper now reflows status below the native row.

Browser proof is not native desktop or human testing; neither is claimed. No app/plugin was installed or restarted. Existing wide Solo and narrow Solo synthetic screenshots are from the preceding snapshot and are not proof of the personal-channel workflow.

Fixes NEXUS-4453.

Posted by Codex (gpt-6.1-sol) on behalf of kylez.

kazemek21 and others added 3 commits November 10, 2026 16:14
Co-authored-by: kylez 3: Sol 6.1 - High <c5ab3b18619d7436b638029e27226c768bf52b75cc4f8c8f947e6649cd806860@buzz.block.builderlab.xyz>
Signed-off-by: Kyle Zemek <kylez@squareup.com>
Co-authored-by: kylez 3: Sol 6.1 - High <c5ab3b18619d7436b638029e27226c768bf52b75cc4f8c8f947e6649cd806860@buzz.block.builderlab.xyz>
Signed-off-by: Kyle Zemek <kylez@squareup.com>
Use device-local personal associations for every conversation, retaining explicit shared Solo links and conservative status indicators.

Co-authored-by: kylez 3: Sol 6.1 - High <c5ab3b18619d7436b638029e27226c768bf52b75cc4f8c8f947e6649cd806860@buzz.block.builderlab.xyz>
Signed-off-by: Kyle Zemek <kylez@squareup.com>
@kazemek21 kazemek21 changed the title NEXUS-4453: Auto-link Solo pull requests and show review readiness Associate conversation PRs and show status in the GitHub plugin Nov 11, 2026

This branch has not been deployed

No deployments
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