blah blah blah
Duplicate of #2753
Hi @flightlevel,
This issue looks similar to #2753.
To prevent issue tracker clutter, this issue will now be closed. If you feel this issue isn't a duplicate of #2753, then feel free to re-open this issue.
Hey @kaso17 @garfield69
Noticed there is a lot of new users to github recently and often they are creating duplicate issues or issues with no content. Suspect the no content ones are often accidents and supplying the duplicate issue may help people instantly for people who don't or find it difficult to search
Had a play with probot https://probot.github.io/
Jackett code here https://glitch.com/edit/#!/jackett
At the moment it can handle two scenarios
-Issue title is exactly that of a previous issue in the last month = duplicate
-No details were provided by the user = no information provided
Not sure if its too brutal just simply closing the issue ??? Can always change that part, maybe give it a go for a week
great!
We should add https://probot.github.io/apps/no-response/
I was planning to change the current error display code (showing the link to open a new github issue) to check the running version vs the latest available version to make sure users are running the latest version before opening an issue.
No-response looks good, will have a play in the next week. Just realized that you can only re-open an issue if YOU are the one who closed it, so will add some logic for that as well
Version checking idea sounds great, its going to become more of a problem now that the docker doesn't update
Updated the bot
Improvements:
-If the bot closed the issue, then a comment from the issue creator will re-open it
-Duplicate issue logic: Rather than use just the oldest in the last month, it will now go for open first, then most comments, then lowest issue number (only looking at issues created in last month with same title)
-Scheduler will look for issues with labels ["More information needed", "No details provided", "Full logs needed"] and if 7 days have passed since the label was applied and the issue creator hasn't commented, then issue gets closed
-Pull requests for new trackers without readme update will remind about readme addition
-Have committed the code to https://github.com/Jackett/Issue-Bot
Most helpful comment
Hey @kaso17 @garfield69
Noticed there is a lot of new users to github recently and often they are creating duplicate issues or issues with no content. Suspect the no content ones are often accidents and supplying the duplicate issue may help people instantly for people who don't or find it difficult to search
Had a play with probot https://probot.github.io/
Jackett code here https://glitch.com/edit/#!/jackett
At the moment it can handle two scenarios
-Issue title is exactly that of a previous issue in the last month = duplicate
-No details were provided by the user = no information provided
Not sure if its too brutal just simply closing the issue ??? Can always change that part, maybe give it a go for a week