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

Track multiple mobile merges through release #1094

New Issue
Closed
opened 2026-08-18 20:21:32 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-18 20:21:32 +00:00
Member
Copy Link

Problem

The mobile post-merge receipt stores one exact commit. Merging a second pull request overwrites the first receipt, so an operator can lose visibility into an earlier failed or unreleased merge. Status also refreshes only when the receipt is opened manually.

Slice

Replace the scalar receipt with a bounded, account-scoped release watchlist. Preserve and independently refresh multiple exact merge commits, prioritize failed checks, expose exact release evidence, and allow individual dismissal. Refresh pending entries while the app is foregrounded without overlapping requests.

Acceptance

  • Two distinct merge commits survive capture and reload; duplicate capture deduplicates.
  • Status responses are matched to their exact commit and cannot update another entry.
  • Failed, running, waiting, and released entries are independently visible and failed entries are prioritized.
  • An operator can dismiss one entry without removing the others.
  • Foreground refresh is single-flight and stops when there is no pending work.
  • Mobile controls remain phone-safe and accessible.
  • Focused tests and the full suite pass.

No existing issue duplicates this behavior: #1092 shipped only one manually refreshed scalar receipt.

## Problem The mobile post-merge receipt stores one exact commit. Merging a second pull request overwrites the first receipt, so an operator can lose visibility into an earlier failed or unreleased merge. Status also refreshes only when the receipt is opened manually. ## Slice Replace the scalar receipt with a bounded, account-scoped release watchlist. Preserve and independently refresh multiple exact merge commits, prioritize failed checks, expose exact release evidence, and allow individual dismissal. Refresh pending entries while the app is foregrounded without overlapping requests. ## Acceptance - Two distinct merge commits survive capture and reload; duplicate capture deduplicates. - Status responses are matched to their exact commit and cannot update another entry. - Failed, running, waiting, and released entries are independently visible and failed entries are prioritized. - An operator can dismiss one entry without removing the others. - Foreground refresh is single-flight and stops when there is no pending work. - Mobile controls remain phone-safe and accessible. - Focused tests and the full suite pass. No existing issue duplicates this behavior: #1092 shipped only one manually refreshed scalar receipt.
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
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#1094
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?