storybookjs
Enterprise
storybook
Sign in / Sign up
Open main menu
Distributed computation caching and task execution are currently disabled for this organization.
Your Enterprise license has expired.
storybook
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
34596
ed2f5dd8 CLI prompt: name the CSS-check story `CssCheck` so telemetry can find it Mirrors the eval-side rename (PR #34595). The prompt now asks the agent to name the CSS-check story `CssCheck` specifically (instead of any story that happens to call `getComputedStyle`). That lets the AI-stories vitest run in core identify the story by name and report its pass/fail result in the \`ai-setup-final-scoring\` telemetry event. Consensus from Slack: keep the story named, drop the tag idea. The story also ends up being educational — a visible example of how to verify CSS loaded.
by Kasper Peulen
K
Succeeded
34596
47b3d606 CLI prompt: reword end-state sentence to avoid biasing toward render() 'Render call' could read as 'you need a render: () => ... function', which is wrong — args stories have no render call and that's exactly the preferred shape for prop-driven components. Softening to 'just rendering the component in the story is enough' keeps the intent (shared preview does the heavy lifting) without steering toward render().
by Kasper Peulen
K
Succeeded
34596
47b3d606 CLI prompt: reword end-state sentence to avoid biasing toward render() 'Render call' could read as 'you need a render: () => ... function', which is wrong — args stories have no render call and that's exactly the preferred shape for prop-driven components. Softening to 'just rendering the component in the story is enough' keeps the intent (shared preview does the heavy lifting) without steering toward render().
by Kasper Peulen
K
Succeeded
34596
47b3d606 CLI prompt: reword end-state sentence to avoid biasing toward render() 'Render call' could read as 'you need a render: () => ... function', which is wrong — args stories have no render call and that's exactly the preferred shape for prop-driven components. Softening to 'just rendering the component in the story is enough' keeps the intent (shared preview does the heavy lifting) without steering toward render().
by Kasper Peulen
K
Previous page
Previous
Next
Next page