github: Adjust settings of the stale workflow #1149
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR proposes a few changes to the
stale
GHA workflow, which was effectively unused due to one of the settings set more conservatively.Specifically, we set
days-before-stale: '-1'
which means that the bot would never attempt to mark issues as stale by itself. That first step was left to us, but I think nobody even realised this is the case and so nobody ever assignedstale
label to an issue/PR.With some older issues being accumulated in the repo, I wanted to update the settings, such that we can more proactively tackle the backlog and communicate expectations to the contributors/reporters.
waiting-response
stale
after 30 days of no response and comment with an updated message, which also states the inactivity periodstale
for over 30 days and received no response, and comments with a message explaining why