feat(source-control): record a report-only Merge-Risk line on each unattended lane merge

Abierto
#13,657 5 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@kyle-sexton ya está trabajando en esto.

Desde el 6/11/2026.

  • #13676 de @kyle-sexton — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

needs-human priority: medium status: ready work-class: scoped

Problem

Owner decision Q57 (#12984, 2026-11-05): do not wire merge-risk's demote into any merge gate yet; record each unattended merge's rating so revert rates per risk level can be measured, then bring Q57 back with those numbers. Nothing records a rating today.

Done when

  • When the unattended merge path arms a merge (.github/scripts/pr-merge/enable-auto-merge.mjs), /review:merge-risk rates the head it arms, and one line is written to the PR body before it enters the merge queue: Merge-Risk: max=<level> demote=<bool> head=<sha> rubric=<review plugin version> rater=<model> checker=<model>. Check: a unit test of the line builder, and one lane merge on main whose squash commit carries the line.
  • The line is report-only: no gate, hold or rung reads it, and a missing or failed rating never blocks or delays the merge (it records Merge-Risk: unrated reason=<reason> instead). Check: a test where the rating fails and the merge still arms.
  • The rating step records its duration and outcome in the lane's existing telemetry, so its cost per merge can be baselined.
  • The model and effort for the rating come from configuration, not code.

Related

  • Refs #12984 (replay results and the recording design; option 1 was chosen)
  • Depends on #13656 for the revert-rate join.
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.