You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2023. It is now read-only.
I've got a question. If I have daysUntilStale=7, why do I often get situations like this, where the stale bot intervenes in an issue a few days after the 7 days mark has passed?
See how in the example below, the bot commented 13 days after the last activity.
OTOH we've noticed surges of stale-bot notifications. That is, we have days without any activity, and then days when there's a significant surge. I'd rather have a few notifications coming in daily than having days with all the notifications from the past few days all at once.
The text was updated successfully, but these errors were encountered:
We've noticed the same thing, and ended up switching to a scheduled GitHub action (https://github.com/actions/stale). This is just my personal theory, but I'm suspecting that GitHub changed an API and stale-bot now has to run in intervals instead of continuously like it did before.
Hi. Thanks for this bot. It really helps.
I've got a question. If I have daysUntilStale=7, why do I often get situations like this, where the stale bot intervenes in an issue a few days after the 7 days mark has passed?
See how in the example below, the bot commented 13 days after the last activity.
OTOH we've noticed surges of stale-bot notifications. That is, we have days without any activity, and then days when there's a significant surge. I'd rather have a few notifications coming in daily than having days with all the notifications from the past few days all at once.
The text was updated successfully, but these errors were encountered: