Don't auto-nag if a bug is fix-optional
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
If a status is set to fix-optional and the bug is still tracked, I don't think we should nag.
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 tracing the auto-nag decision logic and how it reads Bugzilla status values, then inspect how fix-optional bugs are represented while still tracked. Done means a tracked bug with fix-optional status produces no nag, while other statuses retain their existing reminder behavior; add or update the relevant tests if the project has coverage for this logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100