probot-stale not working in test repository

[astrofrog]

I wanted to try out probot-stale via GitHub integrations, so I set it up for this repository:

https://github.com/astrofrog/tmp-coverage

There is an issue that is over a year old so should be marked as stale, but this is not happening. I'm not familiar with how GitHub integrations work exactly, so how often does the bot run? Is there a way to run the bot manually to see a log that might show errors?

[astrofrog]

Ah, it just commented now. What determines the delay before which the bot is run?

[rallytime]

@astrofrog This is another documentation issue I wanted to clear up (as mentioned in #34), but basically once the bot starts running, it will randomly determine when to start commenting on issues/PRs on a given repo, within an hour of starting up.

This is useful for organizations that enable the bot/integration on many repositories within the organization to avoid hitting API limits. Once the bot has started up, it checks for stale issues every hour after that.

Note that if you push up a change to your stale.yml file, it will trigger the bot to skip the wait time and start running immediately. This is also something I want to document.

[bkeepers]

@astrofrog I'm going to go ahead and close this. There is still some work to do on the initial setup experience, but we'll use #34 #36 as the placeholder for that.