Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

pr-pipeline: fix-ci composite activity and its leaves

Cerrado
  • ¿Algo no está bien?
#7,031 1 comentario 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
ci-cd

Línea de trabajo

Start with docs/conventions/pr-pipeline/README.md, especially the Activities section on composite activities, leaves, and the rule that write-effect activities must not execute head code, then read the parent issue #6989. The leaf list is a draft to be finalised from the jobs ci-status runs, and how a leaf that runs PR head code pushes a fix is still reserved for the owner. Done means each leaf has its pipeline-config definition and effect, is enabled per repository, and has a first live run recorded.

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

Descripción

needs-human needs-triage

Refs: #6989

The pr-unblock lane (stage unblock) composes three activities: resolve-conflicts, fix-ci and
address-feedback. Activities are layered: a composite activity lists child activities, and only
leaves run a skill or script with their own effect. This issue tracks the fix-ci composite and
its leaves so none is lost while pr-unblock ships with resolve-conflicts only.

Leaves (draft; final list comes from the jobs ci-status runs)

  • fix-format
  • fix-lint
  • fix-types
  • fix-build
  • fix-tests

Open, owner-reserved

  • How a leaf that must run PR head code (tests, builds) pushes a fix: a read-only diagnose step
    followed by a separate push step, or another split. A write-effect activity must not execute
    head code (docs/conventions/pr-pipeline/README.md, Activities).

Done when

Each leaf is defined in the pipeline config with its effect, enabled per repository, and its
first live run is recorded.

🤖 Generated with Claude Code

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
7 h 23 min
PR fusionados (30 d)
950

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.