nagging about severity of stalled sec-high bugs
Open
Nobody has claimed this yet.
area-Severity
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
We've got a number of bugs with both the sec-high and stalled keywords. AFAICT auto-nag recently started complaining on those about the severity. That seems rather noisy, shouldn't those be filtered out?
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 locating the auto-nag logic that checks bug severity and the handling of the sec-high and stalled keywords. Reproduce the noisy warning with both keywords present, then verify that this combination is excluded from the severity reminder without changing other nag behavior.
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
- 35/100