Processing less than 24 issues per day

[dwijnand]

The limitPerRun configuration option, which limits the number of actions per hour, has a minimum of 1. This means that when enabling stale bot on a repo with lots of old issues, the minimum is getting pings on 24 issues per day.

Does anyone here have ideas how to reduce that?

I'm interested to know if it's possible to get somewhere between 1-5 issues a day, so that they can be reviewed appropriately.

Thanks!

[hiimbex]

You could fork stale and edit it's use of scheduler to utilize these options.

Or you could build this into core stale and open a PR and as long as the default is still an hour, that should be fine.

[dwijnand]

From @bkeepers' comment in #167 (review) this is blocked on having support in https://github.com/probot/scheduler for a per-repository scheduler (tracked as probot/scheduler#32).

GitHub

probot/scheduler

A Probot extension to trigger events on an hourly schedule - probot/scheduler

[dwijnand]

From #167, this requires changes in probot's scheduler library.

As an alternative, can we find a configuration option to make probot skip a run? A blunt option would be "run once a day". That would work for our use case, but would a change like that be accepted?

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

[dwijnand]

This is blocked pending an upstream fix of probot/scheduler#32.

[ncw]

I note that you could do this in a probabilistic way without changing the scheduler by setting limitPerRun = 0.1 and in the code if limitPerRun < 0 compare it against a random number from 0..1 and if it is less than that number do the check, otherwise just return.

[stale]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?