Teddy Katz

:+1:, but it's worth noting that we sometimes forget to remove the `needs info` label from an issue even after info has been provided. It might be good if the...

The bot doesn't have a database, so remembering that type of thing might be tricky. I suppose it could search through its old comments on any given issue. I assume...

I suppose that would be nice, although it's probably not required for the plugin to be useful if it would be easier to implement without that feature.

I'm not opposed to this, but I'm also not convinced that it's necessary based on our current set of plugins. It seems like the only plugin that currently needs any...

> Probot is built by the Github team and they store all the config inside .github folder. That where probot is going to read from. My interpretation of the `.github`...

My point of view is the same as it was in https://github.com/eslint/eslint-github-bot/issues/46#issuecomment-353750457. I don't object to adding repo-specific configuration, but I think it would be a lot better for that...

Sure, feel free.

I've retitled the issue.

I see this issue was assigned to me but I'm not sure of the best way to proceed. My thoughts on the question are the same as they were in...

I think dropping support for point versions of Node is a breaking change for the reason you mentioned (doing a minor upgrade of ESLint shouldn't force you to upgrade Node.js)....