Split running jobs out of History, collapse History - #13
Merged
Conversation
History mixed live runs with finished ones and always rendered in full. Three sections now: Scheduled, Running, and a collapsed-by-default History, bucketed by scheduleBucket() so each schedule lands in exactly one. The polling predicate derives from the same buckets instead of re-encoding the "still moving" rule separately. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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
The dashboard had two sections: Pending and History — and History held both live runs and finished ones, always expanded.
Now three:
pendingprocessing, ortriggeredwith no GitHub conclusion yet<details>collapsed by defaultHow
scheduleBucket(status, runConclusion)intypes/schedule.tsreturns exactly one ofscheduled | running | history, so the sections are a partition — nothing shows twice or disappears.isActive(the poll gate) now derives from those buckets instead of restating the "still moving" rule in a second place; that duplication was why running jobs sat in History.The disclosure uses the native
<details>/<summary>marker — no state, no custom chevron.Notes
lib/crypto.tshas an unrelated uncommitted change in the working tree; deliberately left out of this branch.Verification
tsc --noEmitclean,eslintclean,vitest run84/84 pass. Not exercised in a browser.🤖 Generated with Claude Code