Repository navigation
ci: un último job ci en cada CI compartido para el ruleset de main - #13
Merged
Merged
Conversation
A repository that calls ci-laravel, ci-wordpress or ci-static reports its checks as "ci / <job>". The new closing job "ci" is green only when no job above failed or was cancelled, so the organization ruleset of those repositories asks for one check, "ci / ci". Refs: break 8 Nov 2026 (block 6) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fk5Z8A9Vs7EQFYbkaKgTb3
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
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.
Resumen
Bloque 6 del break (9 nov 2026), con GitHub Flow y los rulesets de organización de
ramas-y-rulesets.md. Un repositorio que llama al CI compartido muestra hoy sus checks comoci / branch,ci / laravel… y un ruleset no puede pedir «todos». Cada CI compartido termina ahora con un jobci, que está en verde solo si nada de lo anterior falló o se canceló. Así el ruleset de esos repositorios pide un solo check:ci / ci.Tarea
Qué cambia
ci-laravel.yml,ci-wordpress.ymlyci-static.yml: un job finalci(needsde todos,if: always()). Falla si algún resultado esfailureocancelled; uno saltado vale, como el de Laravel antes de que exista la app.ci / ci.Cómo probarlo en 2 minutos
ci / ci.ci / branchfalla yci / citambién.Criterios de aceptación
ci / ci.ci / ciestá en rojo si falla cualquier otro job y en verde si los demás pasan o se saltan.Comprobado aquí: los cuatro workflows se leen con
yq, y la lógica del job da verde con «success skipped» y «skipped skipped» y rojo con «failure skipped» y «success cancelled».Riesgos
ci / cise crean después de fusionar.Capturas
No aplica.
Tiempo
Generated by Claude Code