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

[not_landed] Clear BugBot needinfos when prompted patches land on an open bug

Abierto
  • ¿Algo no está bien?
#3,052 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
tooling

Línea de trabajo

Start with the status-based cleanup described in #3003 and #3004, and trace how BugBot-created not_landed needinfos are matched to patches. Define a reliable match using information from the original bot comment, then add coverage for multiple prompted patches, later or obsolete attachments, missing revisions, unrelated flags, and patches that are later backed out.

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

Descripción

Follow-up to #3003, whose initial scope is cleanup on bugs closed as FIXED in #3004.

A patch can land while its Bugzilla bug stays open. In that case, a not_landed needinfo about that patch is no longer actionable, but the status-based cleanup does not remove it.

Clear pending needinfo flags created by not_landed once all patches that prompted that particular request have landed, even if the bug remains open. Leave human-created needinfos and flags created by other BugBot rules untouched.

The key design question is how to identify the original patches reliably. Current attachments alone are insufficient: unrelated patches may be added later, and original attachments may become obsolete. One option to evaluate is including explicit revision links in the original needinfo comment, allowing cleanup to check the patches named in the matching bot comment without custom database tracking. Historical comments without that information should not be cleared based on guesses.

Include coverage for multiple prompted patches, later unrelated attachments, obsolete attachments, missing/inaccessible revisions, and unrelated flags. The design should also consider patches that land and are subsequently backed out.

This is distinct from #2404, which concerns arbitrary pending needinfos on closed bugs.

Lenguaje dominante
Python
Estrellas
69
Forks
93
Merge medio
3 d 11 h
PR fusionados (30 d)
19

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 mozilla/bugbot

Todos los issues de mozilla/bugbot

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.