@Hixie I have the same issue. Did you find a fix at-all?

Nope. :-(

Same here :(

same here...

It is working for me now. My problem is I didn't assign the label for the issue.

so just to check - is this working now? I've just flagged some issues, I won't find out until the 14 day timer expires

It works fine on my side.

Seems to not work again. For example: flutter/flutter#20912

It's still not working for flutter/flutter reliably --- any update here? Thanks!

cc @helinanever

I also recently installed the bot on a new repo and I yet have to see the bot close any issues. I've seen it remove the label when a customer responded, so I know that the bot seems to be configured for my repo. Or does this only apply to labels applied after you configure the bot? If so, I might start seeing issues closed after an additional week or so.

The behaviour of the bot in https://github.com/flutter/flutter/issues is still unreliable. The most common issue is that it fails to close issues at the right time (21 days), e.g. flutter/flutter#10593, or closes them later (after 26 days), e.g. flutter/flutter#47619.

Sometimes it also closes when it shouldn't, e.g. flutter/flutter#38976, or doesn't remove the "waiting for.." label after the author replies, e.g. flutter/flutter#53790.

GitHub

flutter/flutter

Flutter makes it easy and fast to build beautiful apps for mobile and beyond. - flutter/flutter

@helinanever and @Hixie
You guys do notice you didn't use the recommended syntax in the config file do you?
closeComment: >-
Where the recommended syntax is:
closeComment: >

We did not notice at all, good to know.

(Though... why would it sometimes work in that case?)

(Though... why would it sometimes work in that case?)

Thats a very good question! For which i've no answer...
Don't expect this to magically fix your problem, but at least we might be able to exclude this... :)

Just FYI, since I posted, the bot started working for my repo. After a couple of weeks waiting to see if the bot would kick off (I had the period set to 14 days), I changed it to 10 and then it started working all of the sudden.