fix(ci): improve Chromatic workflow#7156
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Docker builds report
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7156 +/- ##
==========================================
+ Coverage 98.27% 98.34% +0.07%
==========================================
Files 1336 1336
Lines 50047 50174 +127
==========================================
+ Hits 49182 49344 +162
+ Misses 865 830 -35 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
f754ead to
e1c776e
Compare
Playwright Test Results (oss - depot-ubuntu-latest-arm-16)Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Failed testsfirefox › tests/sdk-keys-test.pw.ts › SDK Keys Tests › Server-side SDK keys can be created and deleted @oss Details
Playwright Test Results (oss - depot-ubuntu-latest-16)Details
Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)Details
Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
|
- Run on push to main to establish baselines (was PR-only) - autoAcceptChanges on main — no manual review needed for source of truth - Narrow path filter for main push (components, styles, storybook only) - Broad path filter for PRs (frontend/**) to catch indirect regressions - Fix if condition to handle both push and pull_request events Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
e1c776e to
2a70efb
Compare
Changes
Three fixes to the Chromatic CI workflow:
1. Run on push to main
Previously only ran on PRs. Without a main build, Chromatic has no baseline — every PR shows all stories as "new changes" requiring manual acceptance (the 50 pending changes issue).
2. Auto-accept on main
autoAcceptChanges: mainautomatically accepts all changes when merging to main. Main is the source of truth — no manual review needed. Future PRs compare against this auto-updated baseline.3. Narrow path filter
Previously triggered on any
frontend/**change. Now only triggers on files that affect Storybook rendering:frontend/web/components/**frontend/web/styles/**frontend/common/theme/**frontend/documentation/**frontend/.storybook/**E2E tests, configs, and other non-UI files no longer trigger Chromatic.
How did you test this code?
autoAcceptChangesparameter is supported bychromaui/action@v11ifcondition handles both push and pull_request events