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

Advance Today after merging a planned pull request #407

New Issue
Closed
opened 2026-08-09 14:51:38 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-09 14:51:38 +00:00
Member
Copy Link

Problem

The Today session advances after closing a planned issue, but a successful merge of a planned pull request only removes the PR. Mobile operators must leave the active flow, return to My Work, and manually open the next planned item.

User flow

When a mergeable pull request is the active Today item, label the action Merge & next. Only after the server confirms the merge, remove it and advance exactly once to the next planned item. Merging the final item completes the session. Outside an active session, preserve the existing Merge behavior.

Acceptance criteria

  • Active eligible pull requests show Merge & next; outside a session they show Merge.
  • A confirmed merge refreshes without an intermediate session reconciliation and advances exactly once, opening the next item.
  • The final merged item ends the Today session and announces completion.
  • Cancelled, failed, stale-head, or ambiguous merges do not remove or advance.
  • Existing issue close-and-next and non-session merge behavior remain unchanged.
  • Behavioral tests cover the success, final-item, non-session, and failure boundaries.

Evidence / non-duplication

frontend/dashboard.js already completes and advances for issue closure but the merge success path only removes the item. Historical review of 206 issue titles found no merge-to-Today-session advancement. Closest completed work is #161 (assigned PR completion), #240 (review to merge), and #391/#392 (issue close and next); none connects confirmed PR merge to the active Today session.

## Problem The Today session advances after closing a planned issue, but a successful merge of a planned pull request only removes the PR. Mobile operators must leave the active flow, return to My Work, and manually open the next planned item. ## User flow When a mergeable pull request is the active Today item, label the action **Merge & next**. Only after the server confirms the merge, remove it and advance exactly once to the next planned item. Merging the final item completes the session. Outside an active session, preserve the existing **Merge** behavior. ## Acceptance criteria - Active eligible pull requests show **Merge & next**; outside a session they show **Merge**. - A confirmed merge refreshes without an intermediate session reconciliation and advances exactly once, opening the next item. - The final merged item ends the Today session and announces completion. - Cancelled, failed, stale-head, or ambiguous merges do not remove or advance. - Existing issue close-and-next and non-session merge behavior remain unchanged. - Behavioral tests cover the success, final-item, non-session, and failure boundaries. ## Evidence / non-duplication `frontend/dashboard.js` already completes and advances for issue closure but the merge success path only removes the item. Historical review of 206 issue titles found no merge-to-Today-session advancement. Closest completed work is #161 (assigned PR completion), #240 (review to merge), and #391/#392 (issue close and next); none connects confirmed PR merge to the active Today session.
timmy was assigned by rockachopa 2026-08-09 14:51:38 +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#407
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?