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

evidence-refresh: hourly manual dispatches force-push #6428 before its CI finishes, so it never merges

Abierto
  • ¿Algo no está bien?
#6,693 6 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, github-actions, python
Área
ci-cd, devops, documentation

Línea de trabajo

Start with .github/workflows/evidence-refresh.yml, .claude/rules/ci-workflows.md, and docs/ci.md; trace what dispatches the workflow hourly as squid-protocol and inspect how it force-pushes PR #6428. Check how the workflow can detect whether required checks for the current head are still running. Done means hourly dispatches are stopped or documented, refreshes do not push during pending checks, and the bot PR merge guidance is documented.

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

Descripción

bug ci-cd priority: medium scope:infra

What happened

evidence-refresh.yml is meant to run nightly and on demand only (#4825). Since 2026-10-24 it has been started by workflow_dispatch about every hour, about 25 runs, every one with actor and triggering actor squid-protocol (for example runs started at 2026-10-25T17:51, 18:50, 19:59, 21:31, 22:03, 22:52, 22:56 and 2026-10-26T00:00).

Every run force-pushes the bot PR #6428 (auto/evidence-refresh-full) and restarts its CI: det, Db2 shards, ground-truth and the full suite, about an hour in all. The next dispatch lands before the required checks (det, full-suite, ground-truth, mypy-audit, ruff-audit) finish, so #6428 has sat BLOCKED on pending checks and never merges, although auto-merge is enabled on it. Each run also costs about an hour of the shared runner pool (.claude/rules/ci-workflows.md).

A shepherd:merge label added by a person made this worse. Each force-push moved the head, so the shepherd dropped the label as unreviewed and turned auto-merge off, and the next refresh turned it back on. #6691 tried to work around that by letting the App approve its own label; it was closed, see the closing comment there.

To do

  • Find what is dispatching the refresh hourly as squid-protocol (an agent, skill, night-shift tick or box timer) and stop it, or document when a manual dispatch is right.
  • Guard the workflow: a dispatch does not force-push the full-lane bot PR while that PR's required checks for the current head are still running. It either waits, or it pushes nothing. (#6814)
  • Docs: bot PRs merge through their own GitHub auto-merge and never get shepherd:merge (docs/ci.md). (#6814)
    shepherd:merge was removed from #6428 on 2026-10-26.
Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 14 min
PR fusionados (30 d)
967

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 squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.