question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stale to ignore issues if no maintainer has responded

See original GitHub issue

I’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.

  1. 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.
  2. 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:closed
  • Created 5 years ago
  • Reactions:7
  • Comments:18 (2 by maintainers)

github_iconTop GitHub Comments

6reactions
bencomancommented, Jun 20, 2019

Oh it made me laugh to receive a mail about the StaleBot side-lining a ticket about itself.

5reactions
stale[bot]commented, Jun 20, 2019

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

Read more comments on GitHub >

github_iconTop Results From Across the Web

GitHub stale bot considered harmful - Drew DeVault's blog
It's entirely valid to just ignore your bug tracker entirely and leave it up to users to deal with themselves. There is no...
Read more >
I'm not the commenter, but I think you're misinterpreting the intent of ...
I avoid stalebot for the reason you describe, because I want a maintainer to be reading and triaging issues, and I am in...
Read more >
12 Bots To Better Your Open Source Project
Stale. Automatically close stale Issues and Pull Requests that tend to accumulate during a project. After a period of inactivity, a label will ......
Read more >
Prevent stale merge requests from being mergeable - GitLab
Problem to solve. Merge requests specify a particular SHA to merge against in a target branch. As time goes by, the target branch...
Read more >
Enabling a stale issue bot on my GitHub repositories
Another way is to onboard additional maintainers for projects. If there are more reviewers, more work can get done. Reply. Andre Baumeier –...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found