-
Notifications
You must be signed in to change notification settings - Fork 365
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues should be kept active if reactions (ie upvotes) or backlinks #861
Comments
I'd like this feature to be opt-in. Clicking an emoji button to "upvote" an issue or backlinking to it does nothing meaningful to fix the issue. So for me, those actions should still keep the issue stale. |
What about adding an exception if an issue has X upvotes/reactions do not stale? |
We needed this feature for the main CKEditor 5 issue tracker. We rely reactions to track the popularity of issues and implicitly ask for them. This helps keeping the issue threads cleaner while still having some feedback from the community. @gorzelinski implemented the option to count reactions as "activity" in his fork: gorzelinski#1 and we'll soon be testing it. We'll create a PR in this repo soon :) |
AFAIK, it is ready for review. CC: @dsame |
Our entire Zed repo revolves around upvotes (👍) and a democratic process. It would be great if I could say "don't close any issues with more than 5 upvotes." |
Previous issue #613 which ended with the issue closed by the stale-bot.
The problem
If an issue keeps getting upvoted or other repositories keep linking back to the issue, stalebot will not care unless there is a comment which leads to people adding unhelpful comments to the discussion to keep the issue open.
The solution
The stalebot should reset the start-time from the last upvote or backlink on the issue.
The text was updated successfully, but these errors were encountered: