-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggest filing a new bug when an external user comments on a closed bug #1669
base: master
Are you sure you want to change the base?
Conversation
how often does this happen ? my gut feeling is that it is a bit overkill :) (but happy to be wrong) |
39 bugs in the last 60 days. Click to expand the list!
I agree with you. I'm not convinced about the results yet. Many of the cases are false positives (where having the comments is helpful). This is why I marked the PR as a draft. We could go in one of two directions from here:
|
Based on the decision in the last meeting with @marco-c:
For the last point, we could just include them in the email without performing any action (i.e., not posting on the bug), so we can monitor such cases. I will mark them in red. If we see a pattern worth handling, we could take care of it later. @marco-c WDYT? If you agree, I will file a follow-up issue. |
Dry-runThe following bugs have an external comment after being closed:
|
I noticed that many of the comments are spam. It could be helpful to automaticly tag spam comments here before suggesting opening a new bug. @marco-c wdyt? |
Dry-runThe following bug has an external comment after being closed:
|
Oh yes, it would be painful otherwise... |
Resolves #1516
Checklist
to-be-announced
tag added if this is worth announcing