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
In order to close obsolete issues without having to manually go through issues, we should enable Stalebot to comment on issues that haven't been updated in a certain timeframe. If nobody responds or attaches a certain label, i.e. the issue is no longer relevant, the bot will close it.
Proposed config
# Configuration for probot-stale - https://github.com/probot/stale# Configuration options apply to both Issues and Pull Requests.# We configure those individually to match our workflow (see `pulls:` and `issues:`)pulls:
# Number of days of inactivity before a Pull Request becomes staledaysUntilStale: 60# Number of days of inactivity before a Pull Request with the stale label is closed.# Set to false to disable. If disabled, Pull Request still need to be closed manually, but will remain marked as stale.daysUntilClose: 21# Comment to post when marking as stale. Set to `false` to disablemarkComment: > This pull request has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be closed if no further activity occurs. If you intend to work on this pull request, please reopen the PR. Thank you for your contributions.# Comment to post when closing a stale Pull Request.closeComment: > This pull request has been automatically closed due to inactivity. If you are still interested in contributing this, please ensure that it is rebased against the latest branch (usually `main`), all review comments have been addressed and the build is passing.issues:
daysUntilStale: 365# Number of days of inactivity before an Issue with the stale label is closed.# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.daysUntilClose: 21# Comment to post when marking as stale. Set to `false` to disablemarkComment: > This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution.# Comment to post when closing a stale Issue.closeComment: > This issue has been automatically closed due to inactivity. If you have a good use case for this feature, please feel free to reopen the issue.# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)#onlyLabels: []# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disableexemptLabels: []# Set to true to ignore issues in a project (defaults to false)exemptProjects: false# Set to true to ignore issues in a milestone (defaults to false)exemptMilestones: false# Set to true to ignore issues with an assignee (defaults to false)exemptAssignees: false# Label to use when marking as stalestaleLabel: "status: stale"# Comment to post when removing the stale label.# unmarkComment: ># Your comment here.# Limit the number of actions per hour, from 1-30. Default is 30limitPerRun: 30# Limit to only `issues` or `pulls`# only: issues
Deliverables
Enable the bot using the above config
The text was updated successfully, but these errors were encountered:
Unfortunately that does not seem to be possible, users seem to only be able to reopen issues if they closed them themselves. And at the moment stalebot does not provide a solution for that yet either, see probot/stale#205.
In order to close obsolete issues without having to manually go through issues, we should enable Stalebot to comment on issues that haven't been updated in a certain timeframe. If nobody responds or attaches a certain label, i.e. the issue is no longer relevant, the bot will close it.
Proposed config
Deliverables
The text was updated successfully, but these errors were encountered: