fix(ci): AI review lanes skip on a bot commit, leaving the PR head unreviewed for the merge gate
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
- 28/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions
- Área
- ci-cd
Línea de trabajo
Start from the review lanes' trigger conditions and the skip logic for commits authored by bots, and from the merge gate that holds on a skipped lane, which the /source-control:pull-request step uses. Then check why the first ready event on the PR started no CI. Done means one of the two proposed approaches is chosen and documented in the merge gate, and the ready trigger behaviour is explained or fixed. The maintainer has not yet picked an approach, so confirm the direction before writing code.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
On #6913 (2026-10-11), a docs-cleanup commit by melodic-automation-lanes[bot] (1289a56b3a, 4 wording-only lines) landed on the PR head after the last human-driven push. Both AI review lanes ended skipped on that head, apparently because a bot authored the commit. The /source-control:pull-request merge step holds on a skipped review lane, and the standing merge rule requires the AI reviews to have finished on the head. So the PR either deadlocks or merges on an exception. #6913 merged on an exception: the agent read the bot's 4-line diff itself, and the previous head's security review had passed and its code review had posted "No findings".
A related symptom on the same PR: the first ready event started no CI, and the agent had to flip the PR back to draft and to ready again.
Proposed next step
Pick one and document it in the merge gate:
- Run the review lanes on bot commits to PR branches, at least for the docs-cleanup bot.
- Or let the gate carry forward a review verdict from the prior head when the only later commits come from an allowlisted bot and change wording only.
Separately, check why the first ready event did not trigger the lanes.
- Lenguaje dominante
- Shell
- Estrellas
- 22
- Forks
- 2
- Merge medio
- 8 h 25 min
- PR fusionados (30 d)
- 944
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
-
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
-
agent-ready priority: high work-class: scoped
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
melodic-software/claude-code-plugins#7312 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
melodic-software/claude-code-plugins#7288 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de melodic-software/claude-code-plugins
Issues similares
-
Standalone Unix updater reports success when curl fails (`curl | sh` masks the exit status); Windows path is unaffectedPosiblemente ocupada @akhil9tiet la tomó hoy. Abiertobug CLI windows-os
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
openai/codex#54465 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
ChrisTitusTech/dwm-titus#397 ·
Los mantenedores suelen responder en 1 día
-
Translate zstd cheat sheet to frAbiertogood first issue help wanted language:fr translation
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
mrvi0/cli-cheatsheet#268 ·