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

585 CI pipeline executions

Computation time saved

13d 21h

Cache hit rate

89%

Protect cache integrity with sandboxing

Time to Green

53m 56s

Was 1h 6m, improved by 19%

Succeeded
29640
79369d81 Showed archived custom field filters as read-only pills A saved segment on an archived field kept filtering the list while its pill vanished, because the picker only knows active fields. Archived fields the current filter references are now hydrated back as read-only pills: the operator and value stay visible as static segments so the filter reads clearly, but the field is gone from the picker so the pill can only be removed. Read-only is a mode on the shade filter primitives, where the segments render as static text through the same chrome, and the operator control now shares one dropdown implementation with them. The picker's overflow copy routes through the pattern's i18n, and Storybook covers the new segments and states. Custom text fields default to contains, and the review tidy-ups ride along: a stable empty-array reference, removal of dead icon branches, dropping a forbidden dark variant, and restored test globals.
by Rob Lester
Succeeded
29640
1f59627a Showed archived custom field filters as read-only pills A saved segment on an archived field kept filtering the list while its pill vanished, because the picker only knows active fields. Archived fields the current filter references are now hydrated back as read-only pills: the operator and value stay visible as static segments so the filter reads clearly, but the field is gone from the picker so the pill can only be removed. Read-only is a mode on the shade filter primitives, where the segments render as static text through the same chrome, and the operator control now shares one dropdown implementation with them. The picker's overflow copy routes through the pattern's i18n, and Storybook covers the new segments and states. Custom text fields default to contains, and the review tidy-ups ride along: a stable empty-array reference, removal of dead icon branches, dropping a forbidden dark variant, and restored test globals.
by Rob Lester
Failed
29640
1b26863c Showed archived custom field filters as read-only pills A saved segment on an archived field kept filtering the list while its pill vanished, because the picker only knows active fields. Archived fields the current filter references are now hydrated back as read-only pills: the operator and value stay visible as static segments so the filter reads clearly, but the field is gone from the picker so the pill can only be removed. Read-only is a mode on the shade filter primitives, where the segments render as static text through the same chrome, and the operator control now shares one dropdown implementation with them. The picker's overflow copy routes through the pattern's i18n, and Storybook covers the new segments and states. Custom text fields default to contains, and the review tidy-ups ride along: a stable empty-array reference, removal of dead icon branches, dropping a forbidden dark variant, and restored test globals.
by Rob Lester
Failed
29640
cf1d8972 Removed the unused filter group empty state from shade The picker's group emptyState was added for the members Custom fields group, which no longer shows a section when the site has no fields, leaving the whole mechanism without a consumer: FilterEmptyHint, the prop on both group shapes, the hasEmptyStateToShow memo that kept the Add filter button reachable, and the branch in renderPickerGroup. An unused capability with tests and a story behind it reads as supported and invites a caller, and the two live paths carried a condition that could never be true. A group with nothing to add now collapses away, which is what every other group already did.
by Renato Costa
Succeeded
29640
5e3e9fec Showed archived custom field filters as read-only pills A saved segment on an archived field kept filtering the list while its pill vanished, because the picker only knows active fields. Archived fields the current filter references are now hydrated back as read-only pills: the operator and value stay visible as static segments so the filter reads clearly, but the field is gone from the picker so the pill can only be removed. Read-only is a mode on the shade filter primitives, where the segments render as static text through the same chrome, and the operator control now shares one dropdown implementation with them. When the flag is on but no fields exist yet the Custom fields group points at Settings through a shade FilterEmptyHint in the design system's own register, the picker's overflow copy routes through the pattern's i18n, and Storybook covers the new segments and states. Custom text fields default to contains, and the review tidy-ups ride along: a stable empty-array reference, removal of dead icon branches, dropping a forbidden dark variant, and restored test globals.
by Rob Lester
Succeeded
29640
050bc1d6 Showed archived custom field filters as read-only pills A saved segment on an archived field kept filtering the list while its pill vanished, because the picker only knows active fields. Archived fields the current filter references are now hydrated back as read-only pills: the operator and value stay visible as static segments so the filter reads clearly, but the field is gone from the picker so the pill can only be removed. Read-only is a mode on the shade filter primitives, where the segments render as static text through the same chrome, and the operator control now shares one dropdown implementation with them. When the flag is on but no fields exist yet the Custom fields group points at Settings through a shade FilterEmptyHint in the design system's own register, the picker's overflow copy routes through the pattern's i18n, and Storybook covers the new segments and states. Custom text fields default to contains, and the review tidy-ups ride along: a stable empty-array reference, removal of dead icon branches, dropping a forbidden dark variant, and restored test globals.
by Rob Lester
Succeeded
29640
fb383298 Showed archived custom field filters as read-only pills A saved segment on an archived field kept filtering the list while its pill vanished, because the picker only knows active fields. Archived fields the current filter references are now hydrated back as read-only pills: the operator and value stay visible as static segments so the filter reads clearly, but the field is gone from the picker so the pill can only be removed. Read-only is a mode on the shade filter primitives, where the segments render as static text through the same chrome, and the operator control now shares one dropdown implementation with them. When the flag is on but no fields exist yet the Custom fields group points at Settings through a shade FilterEmptyHint in the design system's own register, the picker's overflow copy routes through the pattern's i18n, and Storybook covers the new segments and states. Custom text fields default to contains, and the review tidy-ups ride along: a stable empty-array reference, removal of dead icon branches, dropping a forbidden dark variant, and restored test globals.
by Rob Lester
Failed
29640
4d40c4cb Kept archived custom field filters visible and unconfigured ones discoverable A saved segment could reference a field that was later archived: the predicate kept filtering the list while its pill vanished, because the picker only knows active fields, leaving an invisible active filter. Archived fields the current filter references are now hydrated back as disabled, removable-only pills with an archive icon, the way archived newsletters already are. When the flag is on but no fields exist yet, the Custom fields group points at Settings rather than disappearing, and custom text fields default to contains to match Name and Email. Review tidy-ups ride the same files: a stable empty-array reference, removal of dead icon branches, dropping a forbidden dark variant, and restoring patched test globals.
by Rob Lester
Succeeded
29640
c17ea3a4 Bumped the members-filter NQL pin to the released 0.11.0/0.13.2 The custom-field filter relies on mongo-knex's $elemMatch operator to require a field and its value on the same leaf row, which shipped in @tryghost/mongo-knex 0.11.0 and is pulled in by @tryghost/nql 0.13.2. This pins both. The pnpm override is what forces those versions everywhere: @tryghost/bookshelf-filter resolves an older mongo-knex through its own nql dependency, without the operator, so the filter would break in the full stack until bookshelf-filter itself moves to the newer nql.
by Rob Lester
Succeeded
29640
c17ea3a4 Bumped the members-filter NQL pin to the released 0.11.0/0.13.2 The custom-field filter relies on mongo-knex's $elemMatch operator to require a field and its value on the same leaf row, which shipped in @tryghost/mongo-knex 0.11.0 and is pulled in by @tryghost/nql 0.13.2. This pins both. The pnpm override is what forces those versions everywhere: @tryghost/bookshelf-filter resolves an older mongo-knex through its own nql dependency, without the operator, so the filter would break in the full stack until bookshelf-filter itself moves to the newer nql.
by Rob Lester
Succeeded
29640
3991a0cf Bumped the members-filter NQL pin to the released 0.11.0/0.13.2 The custom-field filter relies on mongo-knex's $elemMatch operator to require a field and its value on the same leaf row, which shipped in @tryghost/mongo-knex 0.11.0 and is pulled in by @tryghost/nql 0.13.2. This pins both. The pnpm override is what forces those versions everywhere: @tryghost/bookshelf-filter resolves an older mongo-knex through its own nql dependency, without the operator, so the filter would break in the full stack until bookshelf-filter itself moves to the newer nql.
by Rob Lester
Succeeded
29640
d440992c Bumped the members-filter NQL pin to the released 0.11.0/0.13.2 The custom-field filter relies on mongo-knex's $elemMatch operator to require a field and its value on the same leaf row, which shipped in @tryghost/mongo-knex 0.11.0 and is pulled in by @tryghost/nql 0.13.2. This pins both. The pnpm override is what forces those versions everywhere: @tryghost/bookshelf-filter resolves an older mongo-knex through its own nql dependency, without the operator, so the filter would break in the full stack until bookshelf-filter itself moves to the newer nql.
by Rob Lester
Succeeded
29640
2a4ee200 Bumped the members-filter NQL pin to the released 0.11.0/0.13.2 The custom-field filter relies on mongo-knex's $elemMatch operator to require a field and its value on the same leaf row, which shipped in @tryghost/mongo-knex 0.11.0 and is pulled in by @tryghost/nql 0.13.2. This pins both. The pnpm override is what forces those versions everywhere: @tryghost/bookshelf-filter resolves an older mongo-knex through its own nql dependency, without the operator, so the filter would break in the full stack until bookshelf-filter itself moves to the newer nql.
by Rob Lester
Succeeded
29640
bcb0f8aa Bumped the members-filter NQL canary to pr192.6 The pre-release of TryGhost/NQL#192 that the custom-field filter depends on was reduced to just the $elemMatch operator (its unused JSON-path half removed) and hardened with a conversion-time validation pass; repoints the catalog and overrides at that pr192.6 build.
by Rob Lester
Succeeded
feat/ber-3792-filter-and-segment-members-by-custom-fields
697ce1ac Merge 4a1e681f9666f905f6cf24ef6b335199700e5d49 into b911708cb038e31c7b086885c96e3f8076da6b57
by Rob Lester
Failed
29640
4a1e681f Filtered custom field parts by is set and is not set A composite field's part could be filtered by value but not by whether it was set, because "is not set" is a same-row non-existence — no leaf for this field and this part — and the positive $elemMatch that expresses "a matching leaf exists" had no negation. Its complement now does, so the transformer unifies onto it: a scalar field is just a leaf at path '', so the whole field, a part, and the whole-field "Any" are the same thing — a set of leaf rows pinned by (custom_field_id, [path], [value]) — and every filter is one $elemMatch over them, positive for exists, $not-wrapped for none. is not set stops being a special case; it is the negation at every level. This drops the bespoke key-clause branch, keeps a since-deleted field matching nothing (a negated empty match would match everyone), and opens is set / is not set on parts in the operator list. Needs the negatable $elemMatch from the pre-release of TryGhost/NQL#192, pinned here.
by Rob Lester
Succeeded
feat/ber-3792-filter-and-segment-members-by-custom-fields
bbd62267 Merge e6f48ab55bd0bf9830ac74e6fb44ab03affa757e into 784f22cbbd2fe52ad7b322251a51f2b4e5a0774e
by Rob Lester
Failed
29640
e6f48ab5 Listed custom fields as their own group in the members filter The filter dropdown hid every custom field behind one generic "Custom field" entry that opened a second picker. Following the design review, each defined field is now named directly in its own "Custom fields" group, so a publisher can search for "Shipping address" instead of knowing that the technical term is the door it hides behind, and picking one is a single click. A scalar field filters on its value; a composite field's pill opens its parts, with an "Any" option that covers the whole-field is set / is not set. The operator set follows the part chosen there, kept valid across a change by an effect because the framework's filter update can't land a value and an operator change in the same tick. This is presentation only: each field still serialises to the same key-and-value grammar, so the backend relation, the transformer, and saved segments are untouched.
by Rob Lester
Succeeded
29640
5a208d24 Served custom field segments in CSV export and bulk actions A saved custom-field segment worked in the members list but broke everywhere else the list feeds a filter: exporting one errored, and a bulk edit or delete over one crashed, because those paths ran the `custom_fields.*` NQL without registering the relation or chaining the transformer that browse sets up. This lifts that setup out of the bread service into a shared applyCustomFieldsFilter, and calls it from the export id lookup and the two bulk paths as well, so a segment behaves the same through all of them. It stays a no-op unless the flag is on and the filter names a custom field, so nothing changes for filters that don't.
by Rob Lester
Succeeded
29640
7c4e577a Added a custom field filter to the members list A single "Custom field" entry in the members filter list stands in for every field a publisher has defined, so the list stays short however many they create. Choosing it opens a cascade in the value area — which field, then (for a composite like an address) which part, then the operator, then the value — composed from the Shade filter segments so it reads as one native filter pill. The operator lives in the cascade because its valid set depends on the field's type, which is chosen there. The predicate serialises to the same key-and-value grammar the backend relation understands, and parses back so a saved segment reopens to the filter it was built from. Behind the membersCustomFields flag.
by Rob Lester