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 42s

632 CI pipeline executions

Computation time saved

13d 21h

Cache hit rate

89%

Protect cache integrity with sandboxing

Time to Green

50m 48s

Was 1h 3m, improved by 20%

Succeeded
30515
60e56201 Fixed editor flashing after confirming leave ref https://github.com/TryGhost/Ghost/pull/30515 Keep the leave confirmation visible until navigation unmounts the editor, including Radix's automatic close and the blocker's proceeding state. This avoids briefly exposing the editor before the posts list appears. Cover React and native hash links in browser tests and delayed navigation with a focused hook regression.
by Steve Larson
Succeeded
30515
e7a4c0de Fixed React editor leave guard races no ref Kept the create URL replacement behind a pending exit so React Router's single blocker cannot discard the writer's destination. Treating frozen and in-flight clean commands as unsaved work also prevents status changes from being dropped on navigation or unload.
by Steve Larson
Succeeded
30515
6fcc1d7e Fixed the editor leave dialog flashing on a silent leave no ref The dialog was wired to the shared guard's own `open`, which is true for any blocked navigation. A dirty draft that the engine saves and clears on the way out is blocked for as long as the decision takes, so the prompt was inserted on the first blocked commit and again as the navigation landed — a leave that is meant to be silent flashed a question the writer never had to answer. It now opens only on the engine's `confirm` verdict. A MutationObserver catches the insertion itself, which a polling locator cannot: it sees a dialog that opens and closes inside one commit. Also: - A re-auth freeze holds a captured command that no dirty content stands in for, so it counts as unsaved work in its own right. - The engine moves dirtiness without going through a patch, so the session refreshes its cached value on every engine state change rather than relying on the two paths coinciding. - The hook's docblock claimed Back was covered. It is not: the shared guard lets a POP through unless the router created the entry, and admin reaches the editor through a native hash anchor. - Covered the cancel branch for an intercepted hash anchor, and the new session subscription: one notification per dirtiness flip, the pending baseline landing, a throwing subscriber, and unsubscribing.
by Steve Larson
Succeeded
30515
6fcc1d7e Fixed the editor leave dialog flashing on a silent leave no ref The dialog was wired to the shared guard's own `open`, which is true for any blocked navigation. A dirty draft that the engine saves and clears on the way out is blocked for as long as the decision takes, so the prompt was inserted on the first blocked commit and again as the navigation landed — a leave that is meant to be silent flashed a question the writer never had to answer. It now opens only on the engine's `confirm` verdict. A MutationObserver catches the insertion itself, which a polling locator cannot: it sees a dialog that opens and closes inside one commit. Also: - A re-auth freeze holds a captured command that no dirty content stands in for, so it counts as unsaved work in its own right. - The engine moves dirtiness without going through a patch, so the session refreshes its cached value on every engine state change rather than relying on the two paths coinciding. - The hook's docblock claimed Back was covered. It is not: the shared guard lets a POP through unless the router created the entry, and admin reaches the editor through a native hash anchor. - Covered the cancel branch for an intercepted hash anchor, and the new session subscription: one notification per dirtiness flip, the pending baseline landing, a throwing subscriber, and unsubscribing.
by Steve Larson
Succeeded
30515
dc492398 Added leave guards to the React post editor no ref Navigating out of the React post editor could silently drop whatever had not reached the server yet: a router link, the back button, a native hash anchor into an Ember-owned route, and a tab close all went through unguarded. Every blocked exit now goes to the save engine's `leaveRequested()`, which finishes or saves outstanding work and answers `proceed` (leaving loses nothing, so the navigation completes silently) or `confirm` (the writer decides). While the engine is deciding, the discard dialog stays shut, so a draft that saves on the way out never flashes a prompt. The session's own URL replace after a create is claimed separately and passes straight through instead of being read as a leave. The guard needs dirtiness to be observable, and it was not: an edit the engine drops (a published post never autosaves) changed no engine state, so nothing re-rendered and the guard never armed. The session now broadcasts dirtiness flips alongside engine state changes.
by Steve Larson