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

Recover closed authored pull requests from mobile Search #1358

New Issue
Closed
opened 2026-08-24 16:51:20 +00:00 by timmy · 0 comments
timmy commented 2026-08-24 16:51:20 +00:00
Owner
Copy Link

Problem

A mobile author can close a pull request and immediately undo from the completion receipt, but after dismissing the receipt, reloading, or switching devices the closed pull disappears from My Work. Search already discovers closed work, yet its recovery action is restricted to issues. The existing authored-pull API already supports a head-guarded reopen.

Product slice

From Search Preview, let the authenticated author reopen a closed, unmerged pull request into My Work. Confirm before mutation, send the preview head SHA, refresh My Work, open the restored native pull workspace, and preserve the underlying Search state for browser Back. Foreign-authored, merged, and already-open pulls remain read-only.

Acceptance

  • At 320x568 and 390x844, a closed unmerged pull authored by the current user shows a >=44px Reopen in My Work action.
  • Confirmation sends exactly one PATCH with expected_head_sha; success refreshes My Work and opens the restored pull workspace.
  • Browser Back returns to the unchanged Search query/filter/result position.
  • Foreign-authored, merged, and open pulls do not expose the action.
  • Rapid taps are single-flight; stale head/state/authorship failures remain truthful and create no phantom row.
  • Focused behavioral and packaged mobile tests cover the flow.

Non-duplication evidence

Current main e4d0cc9 only implements immediate close-receipt recovery (#1356/#1357). Closed-issue Search recovery exists (#547/#548), and Search-to-workspace for already-open pulls exists (#785/#786). Review of all 682 historical issue titles, 672 PR titles, releases through v0.1.0-rc.1640, and recent commits found no closed authored-pull recovery from Search.

## Problem A mobile author can close a pull request and immediately undo from the completion receipt, but after dismissing the receipt, reloading, or switching devices the closed pull disappears from My Work. Search already discovers closed work, yet its recovery action is restricted to issues. The existing authored-pull API already supports a head-guarded reopen. ## Product slice From Search Preview, let the authenticated author reopen a closed, unmerged pull request into My Work. Confirm before mutation, send the preview head SHA, refresh My Work, open the restored native pull workspace, and preserve the underlying Search state for browser Back. Foreign-authored, merged, and already-open pulls remain read-only. ## Acceptance - At 320x568 and 390x844, a closed unmerged pull authored by the current user shows a >=44px `Reopen in My Work` action. - Confirmation sends exactly one PATCH with `expected_head_sha`; success refreshes My Work and opens the restored pull workspace. - Browser Back returns to the unchanged Search query/filter/result position. - Foreign-authored, merged, and open pulls do not expose the action. - Rapid taps are single-flight; stale head/state/authorship failures remain truthful and create no phantom row. - Focused behavioral and packaged mobile tests cover the flow. ## Non-duplication evidence Current main `e4d0cc9` only implements immediate close-receipt recovery (#1356/#1357). Closed-issue Search recovery exists (#547/#548), and Search-to-workspace for already-open pulls exists (#785/#786). Review of all 682 historical issue titles, 672 PR titles, releases through v0.1.0-rc.1640, and recent commits found no closed authored-pull recovery from Search.
timmy self-assigned this 2026-08-24 16:51:20 +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#1358
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?