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

Recover failed post-merge checks from the mobile release receipt #1366

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

Problem

The mobile release receipt tracks an exact merge commit but stops polling at Checks failed and strips safe Gitea Actions recovery metadata. Operators must leave Stackchain to diagnose and retry post-merge release CI.

Vertical slice

Preserve same-forge recovery metadata for exact-commit checks, expose bounded/redacted failure details and exact-commit retry endpoints, and render Review failure / Retry failed check actions in the phone-safe release receipt. A successful retry resumes release polling.

Acceptance tests

  • Failed checks expose only safe same-forge job metadata and remain bound to the captured merge SHA.
  • Failure logs are bounded and credential-redacted.
  • Retry rejects a job no longer failed on the exact commit and queues valid jobs once.
  • Mobile receipt retains evidence on errors, prevents double submit, and resumes polling after retry.
  • 320px layout preserves 44px actions without horizontal overflow.
  • Focused and full suites pass.

Non-duplication evidence

All 686 historical issue titles and recent commits through d4ddac0 were checked. #1092 added exact release tracking, #1354 added pre-merge pull-head CI recovery, and #1364 added source-branch cleanup; none provides post-merge release-check diagnosis/retry. Open PR #1282 is unrelated.

## Problem The mobile release receipt tracks an exact merge commit but stops polling at `Checks failed` and strips safe Gitea Actions recovery metadata. Operators must leave Stackchain to diagnose and retry post-merge release CI. ## Vertical slice Preserve same-forge recovery metadata for exact-commit checks, expose bounded/redacted failure details and exact-commit retry endpoints, and render Review failure / Retry failed check actions in the phone-safe release receipt. A successful retry resumes release polling. ## Acceptance tests - Failed checks expose only safe same-forge job metadata and remain bound to the captured merge SHA. - Failure logs are bounded and credential-redacted. - Retry rejects a job no longer failed on the exact commit and queues valid jobs once. - Mobile receipt retains evidence on errors, prevents double submit, and resumes polling after retry. - 320px layout preserves 44px actions without horizontal overflow. - Focused and full suites pass. ## Non-duplication evidence All 686 historical issue titles and recent commits through `d4ddac0` were checked. #1092 added exact release tracking, #1354 added pre-merge pull-head CI recovery, and #1364 added source-branch cleanup; none provides post-merge release-check diagnosis/retry. Open PR #1282 is unrelated.
timmy self-assigned this 2026-08-24 21:19:33 +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#1366
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?