pr-pipeline: address-feedback composite activity and its leaves
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
- 15/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Área
- ci-cd
Línea de trabajo
This is a tracking issue for the address-feedback composite and its three draft leaves (fix-finding, reply-to-thread, resolve-thread) in the pr-unblock lane, which is parent issue #6989. Start by reading how the pipeline config defines composite and leaf activities for resolve-conflicts and fix-ci, since the payload does not name specific files. Open questions are per-source leaf design and thread-resolution rules, so this needs a maintainer decision before code. Done means each leaf is defined in the config with its effect, enabled per repository, and its first live run recorded.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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 address-feedback
composite and its leaves so none is lost while pr-unblock ships with resolve-conflicts only.
Leaves (draft)
-
fix-finding: push a fix for a review finding (branch write) -
reply-to-thread: answer a thread that needs no code change (pull-request write) -
resolve-thread: resolve a thread after a pushed commit addresses it (pull-request write)
Per review source (Codex, Claude, human), decide whether each source needs its own leaf or an input
to the leaves above. Threads opened by humans are never resolved by a lane.
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
- 8 h 34 min
- PR fusionados (30 d)
- 946
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de melodic-software/claude-code-plugins
-
needs-human needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
melodic-software/claude-code-plugins#7636 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
agent-ready needs-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
melodic-software/claude-code-plugins#7598 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
-
good first issue priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
melodic-software/claude-code-plugins#7530 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs-human priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
melodic-software/claude-code-plugins#7455 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
melodic-software/claude-code-plugins#7351 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de melodic-software/claude-code-plugins
Issues similares
-
documentation needs-triage priority:medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
yeongseon/azure-functions-validation-python#546 ·
Los mantenedores suelen responder en 1 día
-
Page request: dotnet addAbiertohelp wanted new command
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
tldr-pages/tldr#24755 ·
Los mantenedores suelen responder en 1 día
-
afk-ok area:agents size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
enorm-labs/event-junkie#3523 ·
Los mantenedores suelen responder en 1 día
-
Container fails to start when a mounted neo4j.conf uses spaces around `=`Posiblemente ocupada @RaphaelFakhri la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
neo4j/docker-neo4j#596 ·
-
Cookbook: --json recipes with jqAbiertodocumentation good first issue
Dificultad 2/5 Medio día Aptitud para principiantes 78/100
devdavidejesus/btc-toolkit#63 ·
Los mantenedores suelen responder en 1 día