Repository navigation
refactor: solo el CI compartido y la plantilla de PR - #12
Merged
Merged
Conversation
GitHub only tests now: Ploi deploys each repository on Sergio's merge. Removes the deploy-laravel, deploy-wordpress and deploy-static workflows, the deploy-core action, the deploy contract schema and their tests. The three ci-* workflows and the PR template cite page paths of RASGO OS instead of codes, and the checks of this repository are one job, ci. Refs: break 8 Nov 2026 (block 5) 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 5 del break (8 nov 2026). GitHub ya solo prueba: cada repositorio lo despliega Ploi con el merge de Sergio. Este repositorio se queda con los tres CI compartidos y la plantilla de PR, citando rutas de RASGO OS en vez de códigos.
Tarea
Qué cambia
deploy-laravel.yml,deploy-wordpress.yml,deploy-static.yml, la actiondeploy-core(core.sh), el esquemadeploy-contract.jsony sus pruebas.ci-laravel.yml,ci-wordpress.ymlyci-static.yml, con la rama del break admitida hasta que acabe y los mensajes citando5-desarrollo/github.md. La plantilla de PR ya no cita D-082 ni DEV-02 y apunta aspecs/<TAREA>.md(5-desarrollo/specs.md).test.ymlpasa aci.yml, un jobci: la rama y que cada workflow se lee. El README, en corto.Cómo probarlo en 2 minutos
cide esta PR en verde.ci-laravel.yml@main: después de fusionar esta, sucipasa al relanzarlo.Criterios de aceptación
deploy-core.Riesgos
.github/workflows/deploy.yml, que llama adeploy-wordpress.yml: tras este merge ese workflow falla. Se quita en una PR de rasgo-wp-base (va en el mismo bloque si la sesión llega a ese repositorio; si no, queda anotado).ci-laravel.yml.mainde este repositorio pide el checkdeploy-core(el job viejo detest.yml), dejarla pidiendo soloci.Capturas
No aplica.
Tiempo
Generated by Claude Code