Don't update old bugs that are touched and closed straight away
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
I've seen this a few times now, most recently on bug 1362775:
- Bug has sat for a few years without activity.
- Someone finally triages the bug and resolves it (in this case WFM).
- A day or so later, Bugbug comes along and comments that it might be a regression.
Since the bug has been resolved, we shouldn't need to be making sure the regression flag (and others?) are set correctly.
The main pain point here is the extra bugmail & bug noise that is generated and has to be ignored by those watching.
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 Bugbug's regression-check handling for Bugzilla bugs that have already been resolved, using bug 1362775 as the reported example. Confirm that resolved bugs are excluded from regression-flag comments and related metadata updates, and verify that no extra bugmail or bug noise is generated.
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
- 42/100