Overview - Ghost

GhostWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

Ghost

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

GhostWorkspace

Agents
Replay
VCS
Self-Healing

Average execution time

11m 19s

1091 CI pipeline executions

Computation time saved

20d 20h

Cache hit rate

88%

Protect cache integrity with sandboxing

Time to Green

49m 27s

Was 1h 1m, improved by 19%

Succeeded
30759
396ba902 Changed the React editor's capped browses to share their params and pages
by Steve Larson
S
Succeeded
30759
fb8e8954 Updated editor browse params branch from main no ref Included the latest main commit that landed during conflict validation so the pull request remains current and mergeable before review.
by Steve Larson
S
Succeeded
30759
f1eb390b Changed the React editor's capped browses to share their params and pages no ref Three tier browses and two newsletter browses were spelled inline. A query's cache key is the serialized URL, so key order decides whether two sites share one entry: the tiers spellings matched by luck, and the preview's newsletters did not, so opening the preview refetched what the publish flow already held. The shared params now live in one module, and the preview reads the publish flow's full newsletter list and narrows it to the active ones itself. Core caps `limit=all` at 100 rows, so a `limit=all` browse can still carry a next page. The staff picker and the preview's newsletter list both exposed `fetchNextPage` and never called it, truncating staff past the cap and making a newsletter past it read as archived — which then triggered a second lookup by slug. Both now exhaust their pages the way the publish inputs already do, and the staff picker reads as loading until they have. The remaining `limit=all` browses in the editor — the access section's tiers, post snippets and the publish flow's labels — are untouched: whether they should exhaust or search is a product decision rather than a hygiene fix.
by Steve Larson
S