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

Show actionable CI checks in mobile pull reviews #517

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

Problem

Mobile pull-review sheets expose only an aggregate CI failed/pending badge. The backend discards Gitea’s individual commit statuses (job name, description, target URL), so an operator cannot identify the blocker or open its logs without abandoning the focused review flow. Current main has named lint, build-release, and release-candidate checks that can be made actionable.

No open issue or PR covers per-check CI visibility. Review of all historical issue titles and recent commits found adjacent review/CI work, but no detailed check list, safe job links, or in-place check refresh.

Acceptance criteria

  • Requested-review and assigned-pull detail APIs return a bounded, normalized list of individual checks.
  • Unsafe or cross-origin job targets are not exposed as links.
  • Both mobile review sheets summarize checks, put blocking checks first, and expose touch-sized job links without losing review state.
  • Failed/error checks expand automatically; successful checks remain collapsible.
  • Operators can refresh checks in place without clearing drafts, inline comments, reviewed-file progress, or merge gates.
  • At 320px and 390px widths, long check names/descriptions wrap without horizontal overflow.
  • Behavioral API/frontend tests and the full suite pass.
## Problem Mobile pull-review sheets expose only an aggregate `CI failed/pending` badge. The backend discards Gitea’s individual commit statuses (job name, description, target URL), so an operator cannot identify the blocker or open its logs without abandoning the focused review flow. Current main has named `lint`, `build-release`, and `release-candidate` checks that can be made actionable. No open issue or PR covers per-check CI visibility. Review of all historical issue titles and recent commits found adjacent review/CI work, but no detailed check list, safe job links, or in-place check refresh. ## Acceptance criteria - Requested-review and assigned-pull detail APIs return a bounded, normalized list of individual checks. - Unsafe or cross-origin job targets are not exposed as links. - Both mobile review sheets summarize checks, put blocking checks first, and expose touch-sized job links without losing review state. - Failed/error checks expand automatically; successful checks remain collapsible. - Operators can refresh checks in place without clearing drafts, inline comments, reviewed-file progress, or merge gates. - At 320px and 390px widths, long check names/descriptions wrap without horizontal overflow. - Behavioral API/frontend tests and the full suite pass.
timmy self-assigned this 2026-08-10 22:22:06 +00:00
timmy closed this issue 2026-08-10 22:33:53 +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#517
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?