Add 'active git stash' as an action-required category #2

Open
opened 2026-05-23 20:55:21 +00:00 by coilysiren · 0 comments
Owner

Originally filed by @coilysiren on 2026-05-22T18:41:59Z - https://github.com/coilysiren/repo-recall/issues/252

Problem - Stashed git changes are easy to forget. A stash created during one task and not popped silently strands work - there is no ambient signal that a repo has un-popped stashed changes.

Request - Add an action-required category to repo-recall that surfaces any tracked repo with a non-empty git stash list. Each entry should name the repo and the stash count (and ideally the stash messages), so a forgotten stash shows up as action-required rather than staying invisible until someone runs git stash list by hand.

Filed in-session because the sidequest dispatch for this did not start.

_Originally filed by @coilysiren on 2026-05-22T18:41:59Z - [https://github.com/coilysiren/repo-recall/issues/252](https://github.com/coilysiren/repo-recall/issues/252)_ **Problem** - Stashed git changes are easy to forget. A stash created during one task and not popped silently strands work - there is no ambient signal that a repo has un-popped stashed changes. **Request** - Add an action-required category to repo-recall that surfaces any tracked repo with a non-empty `git stash` list. Each entry should name the repo and the stash count (and ideally the stash messages), so a forgotten stash shows up as action-required rather than staying invisible until someone runs `git stash list` by hand. Filed in-session because the sidequest dispatch for this did not start.
coilysiren added
P4
and removed
P3
labels 2026-05-31 07:01:21 +00:00
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
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
coilyco-flight-deck/repo-recall#2
No description provided.