Stale to ignore issues if no maintainer has responded
See original GitHub issueI’ve had a few issues open on the repo probot/friction
over the past few months and noticed that Stale keeps trying to make the issues as stale because no one has responded. In those particular instances, the ticket has been opened and is awaiting some response from a maintainer.
This got me thinking that it might be useful to have some setting (or default) that potentially acts as one of the following.
- If comments have only been made by the OP (this is inclusive of follow ups) then the issue should not be considered for marking as stale.
- If an issue has only received non-maintainer comments then the issue should not be considered for marking as stale.
The above two options are just examples, and each may work better for different project sizes. For example, number 2 might work better for larger projects.
Just a thought I had while seeing multiple Stale notifications pop up across a day because I submitted several issues to the same repo all at once. Every few weeks they tick over as being stale and I’m faced with leaving another comment saying “I think this is still relevant?”. There is argument to say that if I (the OP and only commenter in some situations) haven’t made a comment recently then perhaps it should be treated as stale, this seems like a decision for how people think stale should act and what is considered stale (perhaps a bit meta).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:18 (2 by maintainers)
Top GitHub Comments
Oh it made me laugh to receive a mail about the StaleBot side-lining a ticket about itself.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?