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

Track exact release progress after a mobile pull-request merge #1092

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

User problem

The mobile merge flow immediately advances after showing a transient merged message, but it does not preserve the merge commit or show whether that exact commit passed Actions and produced a release. A successful merge can therefore look shipped even while CI or release publication is still pending or failed.

Scope

  • Return the exact merge commit SHA from the merge API.
  • Persist an account-scoped post-merge release receipt across reloads.
  • Show truthful states for checks running, checks failed, checks passed while waiting for release, and an exact matching release.
  • Match releases to the captured merge commit; never attribute a newer release for another commit.
  • Keep the existing transition to the next Today item.

Acceptance criteria

  • A confirmed mobile merge creates a receipt tied to the PR and exact merge commit.
  • The receipt survives reload only for the confirmed account.
  • Status refresh reports named failing/pending checks and distinguishes checks-passed from release-published.
  • Only a release targeting the captured commit completes the receipt.
  • The mobile sheet has no horizontal overflow, restores focus on close, and exposes 44px controls.
  • Behavioral API/frontend tests are written first and the full suite remains green.

This is distinct from historical release-creation fixes: it adds an operator-visible post-merge evidence flow rather than changing the release workflow itself.

## User problem The mobile merge flow immediately advances after showing a transient merged message, but it does not preserve the merge commit or show whether that exact commit passed Actions and produced a release. A successful merge can therefore look shipped even while CI or release publication is still pending or failed. ## Scope - Return the exact merge commit SHA from the merge API. - Persist an account-scoped post-merge release receipt across reloads. - Show truthful states for checks running, checks failed, checks passed while waiting for release, and an exact matching release. - Match releases to the captured merge commit; never attribute a newer release for another commit. - Keep the existing transition to the next Today item. ## Acceptance criteria - [ ] A confirmed mobile merge creates a receipt tied to the PR and exact merge commit. - [ ] The receipt survives reload only for the confirmed account. - [ ] Status refresh reports named failing/pending checks and distinguishes checks-passed from release-published. - [ ] Only a release targeting the captured commit completes the receipt. - [ ] The mobile sheet has no horizontal overflow, restores focus on close, and exposes 44px controls. - [ ] Behavioral API/frontend tests are written first and the full suite remains green. This is distinct from historical release-creation fixes: it adds an operator-visible post-merge evidence flow rather than changing the release workflow itself.
timmy self-assigned this 2026-08-18 19:41:10 +00:00
timmy closed this issue 2026-08-18 19:49:09 +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#1092
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?