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

Close obsolete authored pull requests from mobile with recovery #1356

New Issue
Closed
opened 2026-08-24 15:54:13 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-24 15:54:13 +00:00
Member
Copy Link

User problem

Authors can publish, revise, review, recover CI, and merge pull requests in the mobile workspace, but cannot close an obsolete authored pull without leaving Stackchain. An accidental close also needs an immediate, safe recovery path.

Acceptance criteria

  • Only the pull author can close an open, unmerged pull at the expected head SHA.
  • The mobile pull workspace exposes a phone-safe confirmed Close action for authored pulls and removes the closed item from My Work.
  • A completion receipt offers one-tap Reopen; reopen is author-only and allowed only while closed and unmerged.
  • Stale heads, changed state, lost authorship, timeouts, and unconfirmed upstream mutations fail truthfully without removing the item.
  • Behavioral API/controller tests and a rendered 320x568 / 390x844 packaged mobile journey cover close and recovery.

Non-duplication evidence

No historical issue/PR title or recent commit covers closing/reopening pull requests. Related #884, #547, and #391 are issue-only flows. All currently open product issues are assigned to other humans.

## User problem Authors can publish, revise, review, recover CI, and merge pull requests in the mobile workspace, but cannot close an obsolete authored pull without leaving Stackchain. An accidental close also needs an immediate, safe recovery path. ## Acceptance criteria - Only the pull author can close an open, unmerged pull at the expected head SHA. - The mobile pull workspace exposes a phone-safe confirmed Close action for authored pulls and removes the closed item from My Work. - A completion receipt offers one-tap Reopen; reopen is author-only and allowed only while closed and unmerged. - Stale heads, changed state, lost authorship, timeouts, and unconfirmed upstream mutations fail truthfully without removing the item. - Behavioral API/controller tests and a rendered 320x568 / 390x844 packaged mobile journey cover close and recovery. ## Non-duplication evidence No historical issue/PR title or recent commit covers closing/reopening pull requests. Related #884, #547, and #391 are issue-only flows. All currently open product issues are assigned to other humans.
timmy was assigned by rockachopa 2026-08-24 15:54:13 +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#1356
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?