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 think it would be great for the bot to operate with exponential backoff, so as to not bother the authors of issues that are expected to take a long time. The feature would consist of setting daysUntilStale to a value that increases with the age of the issue rather than being fixed. For example, an issue can be considered stale if the delay since the last activity exceeds half the age of the issue.
A timeline would look like this:
|------------------------------------------------------------------------------------>
^ ^ ^
creation last activity bot marks issue stale
|------------------------------------------------------------------------------------>
^ ^ ^
creation last activity bot marks issue stale
(user removes "stale" label)
The benefit is that long-term issues and short-term issues can coexist harmoniously, each getting stalebot interventions when appropriate and not too often. For an issue that stays open for a year, a sample schedule of stalebot interventions would be, assuming nobody touches the issue other than for removing the "stale" label:
creation date + 1 month
creation date + 2 months
creation date + 4 months
creation date + 8 months
Compare with a fixed delay of 2 months:
creation date + 2 months (too late?)
creation date + 4 months
creation date + 6 months
creation date + 8 months (too frequent)
creation date + 10 months (too frequent)
creation date + 12 months (too frequent)
What do you think?
The text was updated successfully, but these errors were encountered:
I think it would be great for the bot to operate with exponential backoff, so as to not bother the authors of issues that are expected to take a long time. The feature would consist of setting
daysUntilStale
to a value that increases with the age of the issue rather than being fixed. For example, an issue can be considered stale if the delay since the last activity exceeds half the age of the issue.A timeline would look like this:
The benefit is that long-term issues and short-term issues can coexist harmoniously, each getting stalebot interventions when appropriate and not too often. For an issue that stays open for a year, a sample schedule of stalebot interventions would be, assuming nobody touches the issue other than for removing the "stale" label:
Compare with a fixed delay of 2 months:
What do you think?
The text was updated successfully, but these errors were encountered: