-
Notifications
You must be signed in to change notification settings - Fork 519
-
Notifications
You must be signed in to change notification settings - Fork 519
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
Need to delete/close over 50 empty issues (noise/pollution) #507
Comments
I just closed all the issues linked here. Thank you for doing this! |
I went trough most of the open issues and I have found the following tickets that can be closed (in my opinion) for several reasons (I grouped them): The author haven't returned with more feedback (in more then 1year), it was a question that was answered OR it was an issue because it didn't read the notes. #46 Duplicates of #8 (go tour CLI is not working) "date is wrong" or "random is not working" Suggestion to the languages or general go questions, not related to /tour: & they have answers. |
Done the second batch. I left a couple open for a few issues where I believe we could do better. |
I found a few other solved issues, I missed them in earlier runs. #337 - didn't read the notes Now that a lot of "noise" is gone, I can start finding duplicate issues and maybe do PRs to actually fix stuff. |
Over 150 issues were closed I think, good job @ALTree ! If you want I could go over all the issues one more time and add here the duplicates, or you can close this issue if already done this. Thanks! |
I think we can close here, most of the obviously invalid issues are now closed. Many of the dups are about translation error, those are blocked on a decision on #550. Thanks! |
Hello,
I have identified around 50 issues that most likely were added by mistake, with the standard message , title and no other info. I would list them here to facilitate easy removal for an admin, hopefully.
The problem is that the report button si too visible, and the people that visit the website are not familiar with reporting bug process.
The result is that is very hard to find the real issues/bugs because the list is too poluted
Part 1/2:
#510
#500
#496
#492
#491
#484
#475
#467
#465
#459
#456
#446
#440
#434
#432
#427
#424
#421
#418
#415
#407
#405
#402
#380
#378
#377
#368
#356
#352
#351
#347
#346
#345
The text was updated successfully, but these errors were encountered: