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

New issue

Closed

opened 2026-05-23 20:55:21 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-23 20:55:21 +00:00

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 referenced this issue

2026-05-23 20:55:28 +00:00

recall_action_required: define an ordering contract #60

coilysiren referenced this issue

2026-05-23 20:55:30 +00:00

Native pattern for scheduled auto-mode agents driving the action-required queue #72

coilysiren added the

label

2026-05-31 01:55:07 +00:00

coilysiren added

and removed

labels

2026-06-04 08:16:39 +00:00

coilysiren commented

2026-06-17 08:24:39 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:24:39 +00:00