Provide the triggering Bugzilla comment directly to needinfo follow-up runs
Open
Nobody has claimed this yet.
hackbot
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100