Skip to content

ci: stop auto-accepting Chromatic changes on main - #186

Merged
abernier merged 1 commit into
mainfrom
fix/tailwind-vite-plugin
Aug 18, 2026
Merged

ci: stop auto-accepting Chromatic changes on main#186
abernier merged 1 commit into
mainfrom
fix/tailwind-vite-plugin

Conversation

@abernier

@abernier abernier commented Aug 18, 2026

Copy link
Copy Markdown
Owner

--auto-accept-changes main took whatever landed as the new baseline. That is how a broken shadcn mapping became the reference in #184 with no one looking — the PR build did show it (24 changes), but among 24 legitimate ones from the scaffold refresh, and the merge to main then locked it in.

Changes now get accepted in the PR review, where there is a diff to look at.

Note the trade-off: a push straight to main will leave the UI Tests check red until someone accepts.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FtANJj1cbBZpj12mEXjgSN

`--auto-accept-changes main` took whatever landed as the new baseline, which is
how a broken shadcn mapping became the reference in #184 with no one looking.
Changes get accepted in the PR review, where there is a diff to look at.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FtANJj1cbBZpj12mEXjgSN
@abernier
abernier force-pushed the fix/tailwind-vite-plugin branch from b3e1a7a to b82df77 Compare August 18, 2026 11:10
@abernier abernier changed the title fix: run Tailwind through its Vite plugin, not PostCSS ci: stop auto-accepting Chromatic changes on main Aug 18, 2026
@abernier
abernier merged commit 9bf1892 into main Aug 18, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant