Use Bugzilla webhooks to react to bug openings/changes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
It would make sense especially for scripts such as the spam one or the component one, where we want to act as quickly as possible.
The UI to enable webhooks is located at https://bugzilla.mozilla.org/userprefs.cgi?tab=webhooks.
There is some simple documentation located at https://bugzilla.mozilla.org/page.cgi?id=webhooks.html.
Contributor guide
No contributing guide indexed for this repository
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
Start with the Bugzilla webhook documentation and the existing spam and component scripts mentioned in the issue. Trace how those scripts currently receive or detect bug openings and changes; done means they can react through Bugzilla webhooks as soon as those events occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100