feat: install the toolbox agents, and rename the workflow so one of them works - #4
Merged
Conversation
…hem works Three agents, pinned to EvergineTeam/Evergine.Bindings@1d83f977 -- the merge of toolbox #54, which is the first commit that understands `release.track: tags`. That pin is the reason the toolbox went first: installing against the previous `main` would have given cpp-wrapper-porter a manifest declaring a track its toolbox could not resolve. cpp-wrapper-porter the one this repository exists for. Its step 0 is "if binding.yml has no wrapper: block, do nothing" -- which was true here until the previous commit. binding-updater noops here; there is no generator. Installed because the package installs as a set. ci-doctor see below. Plus the three supporting workflows JoltPhysicsC carries: agentics-maintenance, toolbox-update (the weekly pin bump -- moving the `v1` tag updates nothing on its own), and wrapper-submodule-bump, which completes a porter pull request by moving the gitlink the agent cannot deliver itself. **The workflow is renamed from `Build` to `CI`, and that is a bug fix rather than tidying.** ci-doctor triggers on `workflow_run` filtered to workflows literally named "CI", "CD" or "Sync standards". A repository whose build is called anything else gets an agent that installs, compiles, reports success, and can never fire. JoltPhysicsC has exactly that today: its workflow is "Build JoltC Libraries", and `gh run list --workflow ci-doctor.lock.yml` there returns nothing at all. Zero runs since it was installed. Renaming is free here because no badge or document references the old name; JoltPhysicsC needs its own decision and is filed separately. `gh aw compile --strict`: 3 workflows, 0 errors, 0 warnings.
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.
El tercer eslabón: el agente que aplana la API nueva cuando cesium-native se mueve.
Tres agentes fijados a
EvergineTeam/Evergine.Bindings@1d83f977— el merge del toolbox #54, que es el primer commit que entienderelease.track: tags. Ese pin es la razón de que el toolbox fuera primero: instalarlos contra elmainanterior le habría dado acpp-wrapper-porterun manifiesto que declara un track que su toolbox no sabe resolver.cpp-wrapper-porterbinding.ymlno tiene bloquewrapper:, no hagas nada" — cierto aquí hasta el commit anteriorbinding-updaterci-doctorMás los tres workflows de apoyo que lleva JoltPhysicsC:
agentics-maintenance,toolbox-update(el bump semanal del pin — mover el tagv1no actualiza nada por sí solo) ywrapper-submodule-bump, que completa un PR del porter moviendo el gitlink que el agente no puede entregar.El renombrado es un arreglo, no limpieza
ci-doctorse activa porworkflow_runfiltrado a workflows llamados literalmente"CI","CD"o"Sync standards". Un repositorio cuyo build se llame otra cosa se queda con un agente que se instala, compila, reporta éxito y no puede dispararse nunca.Este se llamaba
Build.Y JoltPhysicsC tiene hoy exactamente el mismo problema — su workflow es
Build JoltC Libraries:devuelve nada. Cero runs desde que se instaló.
Aquí renombrar sale gratis porque ningún badge ni documento referencia el nombre viejo. JoltPhysicsC necesita su propia decisión, y va aparte: una edición local del
.mdla pisaría eltoolbox-updatesemanal, así que el arreglo tiene que vivir en el toolbox o en el nombre del workflow.gh aw compile --strict: 3 workflows, 0 errores, 0 avisos.🤖 Generated with Claude Code