stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Address requested review feedback from mobile pull detail #1338

New Issue
Closed
opened 2026-08-24 06:23:13 +00:00 by timmy · 0 comments
timmy commented 2026-08-24 06:23:13 +00:00
Owner
Copy Link

User problem

Requested-change feedback is visible in mobile pull detail, but authors cannot work through every comment in context, preserve progress, or send one accountable response before requesting another review.

Vertical slice

  • Preserve stable review and inline-comment identities in review data.
  • Add a guided Address feedback pass for requested-change/outdated reviews.
  • Let the author mark every comment Addressed, Needs discussion, or Skip for now with an optional note.
  • Persist progress by repository, pull, review, comment, account, and current head.
  • Generate and post one bounded summary comment with idempotent retry behavior.
  • After confirmed posting, offer a targeted updated-review request and report failures without duplicating the response.

Acceptance

  • Mobile 320x568 and 390x844: one comment at a time, no horizontal overflow, controls at least 44px.
  • Each step focuses the matching changed file and reports unavailable context truthfully.
  • Reload restores exact dispositions and draft notes for the same review/head.
  • Finish is disabled until all comments have a disposition.
  • A changed PR head blocks posting until refreshed.
  • One confirmation posts exactly one summary; retry cannot duplicate it.
  • Updated review targets the original reviewer only after the response is confirmed.
  • Existing feedback display, merge blocking, and full suite stay green.
## User problem Requested-change feedback is visible in mobile pull detail, but authors cannot work through every comment in context, preserve progress, or send one accountable response before requesting another review. ## Vertical slice - Preserve stable review and inline-comment identities in review data. - Add a guided Address feedback pass for requested-change/outdated reviews. - Let the author mark every comment Addressed, Needs discussion, or Skip for now with an optional note. - Persist progress by repository, pull, review, comment, account, and current head. - Generate and post one bounded summary comment with idempotent retry behavior. - After confirmed posting, offer a targeted updated-review request and report failures without duplicating the response. ## Acceptance - Mobile 320x568 and 390x844: one comment at a time, no horizontal overflow, controls at least 44px. - Each step focuses the matching changed file and reports unavailable context truthfully. - Reload restores exact dispositions and draft notes for the same review/head. - Finish is disabled until all comments have a disposition. - A changed PR head blocks posting until refreshed. - One confirmation posts exactly one summary; retry cannot duplicate it. - Updated review targets the original reviewer only after the response is confirmed. - Existing feedback display, merge blocking, and full suite stay green.
timmy self-assigned this 2026-08-24 06:23:13 +00:00
timmy closed this issue 2026-08-24 06:53:20 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1338
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?