Nagging should ask the bug reporter when there is not enough information.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Related to auto_nag/scripts/component.py .
Bug 1803282 got assigned to the JavaScript component.
What was the reasoning to assign this bug to the JavaScript component?
Shouldn't the author of the bug should be nagged in such case, to request more information from the user, in order to make a better triage decision once the author of the bug has answer with actionable information?
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 auto_nag/scripts/component.py and the linked Bugzilla case to understand how component assignment and nagging currently work. Define when a report lacks enough information and verify that the resulting behavior asks the bug reporter for actionable details before triage continues.
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
- Mostly clear
- Newbie friendliness
- 35/100