Loading workspace insights... Statistics interval
7 days30 daysLatest CI Pipeline Executions
ab81b917 CI: Split ci:normal into ci:core and framework/builder split labels
Adds composable CI labels so PRs can run a much smaller, faster pipeline
than ci:normal:
- ci:core runs the internal Storybook e2e tests and every
non-sandbox-specific job (build, unit/story tests, static checks,
chromatic, benchmarks, test-storybooks, init-empty) - i.e. the normal
workflow minus all sandbox jobs.
- ci:<framework> (ci:react, ci:vue3, ci:angular, ci:svelte, ci:html,
ci:preact, ci:web-components, ci:solid) runs ALL sandboxes for that
framework, drawn from the complete (daily) template pool.
- ci:<builder> (ci:vite, ci:webpack, ci:rsbuild) runs ALL sandboxes for
that builder.
Split labels compose: the trigger workflow joins them into a single
`+`-separated workflow value (e.g. core+react) so one pipeline - and one
completion status check - covers the union of the selected atoms. The
legacy cadence labels (ci:normal/merged/daily/docs) still work unchanged
and take precedence over split labels when both are present; the
dangerfile now rejects that mix and otherwise accepts split labels in
place of a cadence label.
The CircleCI `workflow` pipeline parameter becomes a plain string
(validated in scripts/ci/main.ts, which fails setup loudly on unknown
atoms). Framework/builder atoms are derived from each sandbox template's
expected renderer/builder metadata, with both Angular packages mapping
to the single `angular` atom. Legacy workflows generate byte-identical
configs apart from the parameter type change.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JDwFN1kYSqVTZah1BvKQKu