Provide the triggering Bugzilla comment directly to needinfo follow-up runs

Open
#6,696 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api, backend

Research direction

Trace the BMO needinfo webhook handling and compare it with the existing Phabricator follow-up run flow. Identify where the bug-fix run is created, then pass the triggering comment's content and ID through that flow; done means the run receives the exact associated comment without requester-and-timestamp matching.

Written by the indexing model from the issue text.

Description

hackbot

BMO sends needinfo changes and their associated comments as separate webhook events. As a temporary solution, the agent uses the requester and timestamp to find the corresponding comment.
Improve this flow so the bug-fix run receives the exact triggering comment content and ID, similar to Phabricator follow-up runs.

Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 11h
Merged PRs (30d)
61

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.