Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#3,052 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
tooling

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
69
Fork
93
Merge medio
3g 7h
PR unite (30g)
20

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di mozilla/bugbot

Tutte le issue di mozilla/bugbot

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.