Probot not closing issues
See original GitHub issueHeya!
First of all, thanks for probot - it’s amazing!
I’ve had it installed and running on ts-loader for a couple of weeks now. It started out all guns blazing, marking things as wontfix and then closing them a week later. However it appears to have stopped closing older issues. I wonder if you might have any idea why? This is my stale.yml
https://github.com/TypeStrong/ts-loader/blob/master/.github/stale.yml
And here’s my issues: https://github.com/TypeStrong/ts-loader/issues
As you can see lots of older issues are being left as is…
For example this one: https://github.com/TypeStrong/ts-loader/issues/54
Is marked as stale but hasn’t been closed. I can’t work out why…
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Stale bot not closing issues #199 - GitHub
On April 10th, 2019 I setup stale bot to mark issues as stale, and then auto close them. It's been almost 2 weeks...
Read more >How To Fix ProBot Not Responding? 8 Fixes To Try! - Deasilex
To fix ProBot not responding, check whether it is available on the user list, check Discord permission, check Discord volume level, close all...
Read more >No Response - Probot
The intent of this app is to close issues that have not received a response to a maintainer's request for more information. Many...
Read more >Pro-bot not responding : r/discordbot - Reddit
Pro bot hasn't been responding since yesterday and I thought it was just a update but I've already switched through multiple devices and ......
Read more >Newest 'probot' Questions - Stack Overflow
GitHub ERROR probot: Integration not found, documentation_url. I had issues with authentication when working with GitHub's Probot app. When I ran the app...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tcbyrd Thanks. It works after setting closeComment to false
@johnnyreilly That issue isn’t labeled
wontfix
. The call to add the label probably failed while we were dealing with OOM issues, and since the bot’s comment was added < 60 days ago it hasn’t come up in the search for stale issues. Tomorrow is 60 days since Jan 19th, so it should get labeled again on tomorrow’s sweep, or you can mark itwontfix
manually today to see if it gets auto-closed on the next sweep. Providing a report of what Stale is doing on your repo is something I’m hoping to add as well. Right now if anything goes wrong it just fails silently with no way to re-try.