Add status sorting, stale status, batch delete, and spec-driven display#14
Merged
Add status sorting, stale status, batch delete, and spec-driven display#14
Conversation
…ew=purple, closed=dimmed red
1515a44 to
ea05ef9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
flow statustable by status group (open → in-progress → in-review → stale → closed), then by created date descending within each groupflow delete ws1 ws2 ws3~/.flow/cache/status.jsonfor instant pre-sorted display on subsequent runsWhy
Status output was unsorted and colors/labels were scattered across multiple Go files. This makes the status table easier to scan at a glance, introduces the stale lifecycle state, speeds up repeat runs with caching, and ensures custom specs fully control the display without needing code changes.
Ref
Builds on #11 (live-updating table)