[no_severity_nag] Exclude security bugs instead of all confidential bugs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Following up on https://github.com/mozilla/bugbot/pull/2536#discussion_r1831467039
Currently, we depend on the "sec": false config to exclude security bugs, which exclude confidential bugs as well (see https://github.com/mozilla/bugbot/pull/2536#discussion_r1831619083)
If we decide to go with this route, we may want to change the behaviour of the "sec": false config instead of having a custom fix to the no_severity_nag rule only.
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 discussion on pull request 2536 and trace the "sec": false configuration and the no_severity_nag rule. Determine whether the change belongs in the shared security filtering behavior or only in that rule. Done means security bugs are excluded without excluding confidential non-security bugs.
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
- Needs clarification
- Newbie friendliness
- 35/100