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

Keep a Following change for later and continue review #1320

New Issue
Closed
opened 2026-08-23 20:04:41 +00:00 by timmy · 0 comments
timmy commented 2026-08-23 20:04:41 +00:00
Owner
Copy Link

Problem

Following marks a changed item seen as soon as its preview loads. During a phone review pass, an operator who cannot act yet has no non-destructive disposition: closing loses the item from the unseen queue, while stopping watch removes it entirely.

Slice

Add a Following-only Keep for later & next action. It conditionally restores the exact loaded revision as unseen, skips it for the current captured pass, and advances to the next changed item without changing Gitea state or watch status.

Acceptance

  • Keeping restores only the exact loaded revision; newer activity stays unseen and cannot be overwritten.
  • Success advances to the next captured item without looping to the kept item in the same pass.
  • The kept item remains counted and appears in the next review pass.
  • Failure leaves the preview open, does not advance, and exposes a retryable status.
  • The action appears only in Following review, is at least 44px at 320x568 and 390x844, and causes no horizontal overflow.
  • Focused store/API/frontend/mobile tests and the full suite pass.

Non-duplication

Issue-title history through #1319 and recent Following commits cover changed-first ordering, sequential review, retirement, notifications, and alert routing, but no non-destructive keep/defer disposition.

## Problem Following marks a changed item seen as soon as its preview loads. During a phone review pass, an operator who cannot act yet has no non-destructive disposition: closing loses the item from the unseen queue, while stopping watch removes it entirely. ## Slice Add a Following-only **Keep for later & next** action. It conditionally restores the exact loaded revision as unseen, skips it for the current captured pass, and advances to the next changed item without changing Gitea state or watch status. ## Acceptance - Keeping restores only the exact loaded revision; newer activity stays unseen and cannot be overwritten. - Success advances to the next captured item without looping to the kept item in the same pass. - The kept item remains counted and appears in the next review pass. - Failure leaves the preview open, does not advance, and exposes a retryable status. - The action appears only in Following review, is at least 44px at 320x568 and 390x844, and causes no horizontal overflow. - Focused store/API/frontend/mobile tests and the full suite pass. ## Non-duplication Issue-title history through #1319 and recent Following commits cover changed-first ordering, sequential review, retirement, notifications, and alert routing, but no non-destructive keep/defer disposition.
timmy self-assigned this 2026-08-23 20:04:41 +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#1320
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?