Repository navigation
ci: quita Chromatic; compuerta = build de Storybook, PRs con auto-merge - #44
Merged
Merged
Conversation
Decisión de André (2026-10-12): «creo q no lo necesitamos tbh, q se mergee automático». Chromatic agotó la cuota del plan y dejaba «UI Tests» PENDING para siempre (ui#43). ci.yml corre build-storybook como compuerta; typecheck y tests como señal (main ya traía 3 errores de tsc y 2 tests rojos). El Storybook publicado sigue en Cloudflare Pages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Decisión de André (2026-10-12): sin Chromatic, que los PRs se mergeen solos.
chromatic.ymly la dependenciachromatic. La cuota se agotó y el status «UI Tests» quedaba PENDING para siempre (bloqueaba feat(ToolInvocation): tarjeta plegable para tool calls de IA + ToolInvocationGroup #43).ci.yml:npm run build-storybookes la compuerta (lo único que Chromatic validaba en la práctica, porque ya auto-aceptaba diffs).typecheckytestcorren como señal: enmainya fallan hoy (3 errores de tsc, 2 tests), medido local.deploy.yml), sin cambios.Verificado local:
npm run build-storybook→ exit 0.