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

Make assigned pull request sheets read-first with on-demand review #217

New Issue
Closed
opened 2026-08-07 17:51:56 +00:00 by timmy · 0 comments
timmy commented 2026-08-07 17:51:56 +00:00
Owner
Copy Link

Problem

Opening an assigned pull request currently blocks its description and conversation on files, status, and raw diff retrieval, then places changed files before discussion. On mobile, a large or slow diff delays the core read-and-reply flow and forces long scrolling before conversation.

Evidence on current origin/main:

  • src/gitea_proxy.py eagerly loads files, status, conversation, and raw diff in one detail request.
  • frontend/index.html renders changed files before full conversation.
  • Historical review of 112 issues and recent commits found review/merge, complete conversations, and requested-review resilience, but no read-first assigned-PR hierarchy or lazy review payload.

Acceptance criteria

  • Opening an assigned PR renders metadata/body and conversation without requesting changed files, CI status, or raw diff.
  • Description and reply flow appear before a collapsed Review & merge disclosure.
  • First disclosure expansion loads review data once for the current PR head; failures remain scoped to the disclosure with Retry.
  • Reading, replying, routing, and opening in Gitea remain usable when review data fails.
  • Existing all-files-reviewed, fresh-head, CI, and mergeability gates remain mandatory.
  • Behavioral API/frontend tests and the full suite pass; rendered mobile widths have no horizontal overflow.
## Problem Opening an assigned pull request currently blocks its description and conversation on files, status, and raw diff retrieval, then places changed files before discussion. On mobile, a large or slow diff delays the core read-and-reply flow and forces long scrolling before conversation. Evidence on current `origin/main`: - `src/gitea_proxy.py` eagerly loads files, status, conversation, and raw diff in one detail request. - `frontend/index.html` renders changed files before full conversation. - Historical review of 112 issues and recent commits found review/merge, complete conversations, and requested-review resilience, but no read-first assigned-PR hierarchy or lazy review payload. ## Acceptance criteria - Opening an assigned PR renders metadata/body and conversation without requesting changed files, CI status, or raw diff. - Description and reply flow appear before a collapsed **Review & merge** disclosure. - First disclosure expansion loads review data once for the current PR head; failures remain scoped to the disclosure with Retry. - Reading, replying, routing, and opening in Gitea remain usable when review data fails. - Existing all-files-reviewed, fresh-head, CI, and mergeability gates remain mandatory. - Behavioral API/frontend tests and the full suite pass; rendered mobile widths have no horizontal overflow.
timmy self-assigned this 2026-08-07 17:51:56 +00:00
timmy closed this issue 2026-08-07 18:01:16 +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#217
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?