Bugbot shouldn't needinfo regression-assignee if they already touched the bug recently / after the regression was marked up / if they were the one who linked the regressing bug
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
See https://bugzilla.mozilla.org/show_bug.cgi?id=1976320#c5 . I had already identified that "I broke it" and explicitly asked other folks to come up with a verdict on the severity of the breakage - there wasn't really a point to bugbot needinfo'ing me.
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 linked Bugzilla report, especially comment 5, to understand the regression-assignee scenario and the existing needinfo behavior. Trace the bugbot entry point that decides when to needinfo the regression assignee; done means it skips that request when the assignee recently touched the bug, acted after the regression was marked, or linked the regressing bug.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100