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

docs(source-control): define when a push needs a fresh AI review round

Cerrado
  • ¿Algo no está bien?
#6,632 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@melodic-automation-lanes ya está trabajando en esto.

Desde el 18/10/2026.

  • #8050 de @melodic-automation-lanes — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
50/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell
Área
documentation

Línea de trabajo

Start with plugins/source-control/skills/pull-request and read the B2 rule, then inspect the PR monitor and the draft-PR guidance in AGENTS.md. Define the merge-commit diff test and distinguish clean merges or allowed-only file changes from code conflict resolutions; done when the skill states the rule and the monitor applies it.

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

Descripción

needs-human needs-triage

The B2 rule in plugins/source-control/skills/pull-request treats an AI review lane as absent when it is green but posted nothing for the current head. On 2026-10-07 every merge-main push and every push that only added changelog fragments waited about 5 minutes for the lanes to re-run on code they had already reviewed. ci-status is the only required check (AGENTS.md, "Open a pull request as a draft").

An interim rule, "skip the lane wait on merge-only pushes", let #6516 merge after a merge push that had resolved a real conflict in lib/docs-cache.sh. A separate review found the resolution clean, but the auto-mode classifier flagged it as "Merge Without Review".

Proposal: state the rule in the skill.

  • A push needs a fresh review round when it changes reviewed content. Any conflict resolution in code counts as changing reviewed content.
  • A merge of main needs no fresh round when it merged cleanly, or when the only files it changed were CHANGELOG files, plugin.json versions or .changes fragments.
  • Give the test: the diff of the merge commit against its main parent, limited to non-changelog paths, is empty.

Acceptance: the skill gives the test, and the PR monitor applies it.

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
8 h 44 min
PR fusionados (30 d)
926

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.