Some triagers self-assign bugs to say "I'm investigating it" and so in this case "assigned" doesn't mean "confirmed"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
For reference:
https://bugzilla.mozilla.org/show_bug.cgi?id=1531694
In such a case we should blacklist this component.
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 by reading the linked Bugzilla report to understand why assignment does not confirm a bug. Then locate the bot's handling of assigned Bugzilla bugs and its component blacklist configuration; done means the referenced component is excluded from confirmation logic and the behavior is covered by an appropriate regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100