Pre-push gate: every agent commit names who built and reviewed it

Abierto
  • ¿Algo no está bien?
#510 0 comentarios 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, rust
Área
ci-cd, tooling

Línea de trabajo

Start by reading the committed .githooks setup and the handoff brief template; the issue does not name their paths or a test entry point. Check how the gate identifies new commits pushed to develop or a release train and recognizes the required trailers. Done means a test demonstrates failure without both trailers and success with them, the template includes the trailer lines, and the first week of develop is verified as described.

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

Descripción

Why

On 23 October we agreed that every agent commit names who built it and who reviewed it, with Built-by: and Reviewed-by: <reviewer> <review id> trailers. None of the 229 commits on develop from 24 to 30 October has either trailer (git log --since=2026-10-24T00:00-05:00 origin/develop, checked 30 October). An agreement that people must remember did not hold, so a check replaces it.

Change

The committed pre-push gate (.githooks) refuses a push to develop or a release train when a new commit from an agent lane has no Built-by: or no Reviewed-by: trailer. The gate names each commit that fails and the trailer it needs. Commits that a person makes by hand state that in a Built-by: trailer too. History is not rewritten.

Done means

  • The gate fails on a test commit without the trailers and passes on one with both (a test shows fail before and pass after).
  • The handoff brief template gives the trailer lines.
  • The first week of develop after the change has the trailers on every new commit (git log count in this issue).
Lenguaje dominante
Rust
Estrellas
6
Forks
2
Merge medio
1 d 3 h
PR fusionados (30 d)
42

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 elastos/elastos-runtime

Todos los issues de elastos/elastos-runtime

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.