ci(lanes): run every model lane on the same key, subscription and fallback chain

Abierto
  • ¿Algo no está bien?
#13,586 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, github-actions, shell
Área
ci-cd

Línea de trabajo

Start by reading the listed workflow files and the ci-workflows run-claude-cli action, especially the cited line ranges, to map how each lane passes credentials and handles handoffs. Then inspect the existing workflow tests and add coverage that fails when a model-running workflow skips a leg or passes credentials outside the shared mechanism. Done means all nine listed lanes use the same three-leg chain and triggers, and the release lane no longer has a separate credit-stop skip or outdated header.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: security priority: medium status: needs-decision work-class: structural

No related issue: owner decision in the Automation Lanes session, 2026-11-05.

Owner decision (verbatim)

The owner asked, in session: "if anything fails on API credit, it should always roll back to the subscription. If that fails, there's a fallback subscription. Did we have that in place for all of these automations?"

Asked as an AskUserQuestion pick, Q1, which named the release lane's outside-authored changelog input and rule R220. Owner's pick, verbatim: "All nine (Recommended)".

Then, verbatim: "I want them all to be consistent and uniform."

This loosens R220 for upstream-apply-changelog.yml: that lane now gets the subscription and fallback legs. The owner made this pick in their own words, in the session.

Gap (read at origin/main, 2026-11-05)

Every other model lane already runs API key, then role subscription, then FALLBACK_CLAUDE_CODE_OAUTH_TOKEN. It hands off on a credit stop or a 401/402, and on the subscription leg also on a limit stop (ci-workflows run-claude-cli action.yml:7-16; pr-run-activity-read.yml:10-17). These do not:

Workflow Legs today
upstream-apply-changelog.yml (both model legs) key only (:352, :634; :152-156 skips a credit-stopped key)
pr-unblock.yml adjudicate-feedback key only (:1858-1862)
intake-triage.yml refine-issue key, then subscription, with no fallback (:1116-1120)
pr-verify-capture.yml key, then subscription, with no fallback (:37-38)
post-merge-test-mutation.yml subscription only
maintenance-tidy-code-upkeep.yml subscription only
maintenance-measure-skill-edit.yml subscription only
eval-browser-dispatch.yml subscription only
eval-hill-climb-pass.yml subscription only

Done when

  • Every model-running workflow runs the same three-leg chain through the same mechanism: role API key, then role subscription, then FALLBACK_CLAUDE_CODE_OAUTH_TOKEN, with the same handoff triggers. No lane keeps its own variant.
  • A test fails when a model-running workflow lacks a leg, or passes credentials outside that mechanism.
  • The release lane's credit-stop skip is removed or reduced to the shared key-credit gate, and its header no longer says it has no subscription leg.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
1 h 18 min
PR fusionados (30 d)
942

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.