Support editing GitHub issue assignees - #708
Merged
Merged
Conversation
Pre-commit hook ran. Total eslint: 3, total circular: 0
Harry19081
marked this pull request as ready for review
August 6, 2026 12:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
GitHub issue detail views can display assignees, but users cannot edit them consistently from the chat, work-management, and workstation surfaces. The detail-state hook also lacks a shared assignee option model and mutation lifecycle.
Solution
Add a shared assignee normalizer and extend the GitHub issue detail state with assignee discovery, selection, optimistic mutation state, and error handling. Wire the resulting controls through the chat panel, work-management mutation bridge, workstation source-control views, and unified issue renderer so all issue-detail entry points share the same behavior.
Potential risks
Assignee updates still depend on repository permissions and GitHub API availability; failed mutations retain the server-backed value and surface the existing error path. The visual selector states have not been manually exercised in the desktop app, so this PR remains a draft pending UI evidence.
Verification
pnpm exec vitest run src/modules/shared/hooks/useGitHubIssueDetailState.test.ts— passed (4 tests).lint-staged— passed for all 8 changed files.