Handle cases where the bot proposes a severity increase and the developers ignore
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
We were discussing about this and how to best handle cases where the bot proposes an increase, the developers ignore it or set it to a low severity (like S3), and then later we get more duplicates.
@calixteman said:
A possibility is to add the number of dup in the comment made by the bot, and if at some point prev_dup_num +whatever >= current_num then nag again or nag when num of bugs is a multiple of 3 or whatever
we can have different strategies based on the number of dups
3 => reset, 6 => reset + tracking request, ... something like that
Originally posted by @marco-c in https://github.com/mozilla/relman-auto-nag/issues/1184#issuecomment-1019921816
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 discussion referenced from relman-auto-nag issue #1184 and tracing the bot's existing severity-increase and duplicate-handling behavior. Before implementation, agree on the strategy for repeated duplicates and ignored or downgraded proposals; done means that agreed strategy is implemented and its behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100