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

Refresh pull request checks without reloading review data #521

New Issue
Closed
opened 2026-08-10 23:19:27 +00:00 by timmy · 0 comments
timmy commented 2026-08-10 23:19:27 +00:00
Owner
Copy Link

Problem

Refreshing CI checks in an assigned pull or requested review currently reloads files, reviews, and the full diff. A slow diff can therefore fail an otherwise healthy status refresh and repeated mobile refreshes redownload expensive immutable review data.

Scope

  • Add bounded status-only check endpoints for assigned pulls and requested reviews.
  • Refresh normalized checks and merge gates without replacing loaded review content.
  • If the head SHA changes, keep the old diff and require an explicit full reload before review or merge.
  • Preserve composer, reviewed-file progress, and inline-comment state during refresh.

Acceptance

  • Status refresh calls pull/status upstreams but never files, reviews, or diff.
  • Pending-to-success updates checks and merge eligibility in place.
  • Changed head disables consequential actions and shows reload guidance.
  • Focused backend/frontend behavioral tests and full suite pass.

This is distinct from #517, which introduced actionable checks but refreshes them through the full review-data path, and #127, which bounded the complete initial review load.

## Problem Refreshing CI checks in an assigned pull or requested review currently reloads files, reviews, and the full diff. A slow diff can therefore fail an otherwise healthy status refresh and repeated mobile refreshes redownload expensive immutable review data. ## Scope - Add bounded status-only check endpoints for assigned pulls and requested reviews. - Refresh normalized checks and merge gates without replacing loaded review content. - If the head SHA changes, keep the old diff and require an explicit full reload before review or merge. - Preserve composer, reviewed-file progress, and inline-comment state during refresh. ## Acceptance - Status refresh calls pull/status upstreams but never files, reviews, or diff. - Pending-to-success updates checks and merge eligibility in place. - Changed head disables consequential actions and shows reload guidance. - Focused backend/frontend behavioral tests and full suite pass. This is distinct from #517, which introduced actionable checks but refreshes them through the full review-data path, and #127, which bounded the complete initial review load.
timmy self-assigned this 2026-08-10 23:19:27 +00:00
timmy closed this issue 2026-08-10 23:28:27 +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#521
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?