Stop stalebot from nagging on the same issues - #58418
Merged
Merged
Conversation
We've been doing it manually when the stalebot keeps coming back to deep-sitting bugs that we'll pretty much never fix accidentally / in passing, now we're automating it: the stalebot will lay off the bugs that have already gone through the cycle of “reported — stalebot asks to confirm — the users confirm” once. This might need to be complemented with a yearly sweep of the `never stale` issues as a sanity check, but first we just shed the manual work.
MrSubidubi
approved these changes
Jun 3, 2026
TomPlanche
pushed a commit
to TomPlanche/zed
that referenced
this pull request
Jun 8, 2026
We've been doing it manually when the stalebot keeps coming back to deep-sitting bugs that we'll pretty much never fix accidentally / in passing, now we're automating it: the stalebot will lay off the bugs that have already gone through the cycle of “reported — stalebot asks to confirm — the users confirm” once. This might need to be complemented with a yearly sweep of the `never stale` issues as a sanity check, but first we just shed the manual work. Release Notes: - N/A
This was referenced Jun 10, 2026
This was referenced Jun 18, 2026
Closed
This was referenced Jul 1, 2026
This was referenced Jul 10, 2026
jonx
pushed a commit
to jonx/zed-aros
that referenced
this pull request
Jul 17, 2026
We've been doing it manually when the stalebot keeps coming back to deep-sitting bugs that we'll pretty much never fix accidentally / in passing, now we're automating it: the stalebot will lay off the bugs that have already gone through the cycle of “reported — stalebot asks to confirm — the users confirm” once. This might need to be complemented with a yearly sweep of the `never stale` issues as a sanity check, but first we just shed the manual work. Release Notes: - N/A
jolutz
pushed a commit
to jolutz/zed
that referenced
this pull request
Aug 8, 2026
We've been doing it manually when the stalebot keeps coming back to deep-sitting bugs that we'll pretty much never fix accidentally / in passing, now we're automating it: the stalebot will lay off the bugs that have already gone through the cycle of “reported — stalebot asks to confirm — the users confirm” once. This might need to be complemented with a yearly sweep of the `never stale` issues as a sanity check, but first we just shed the manual work. Release Notes: - N/A
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We've been doing it manually when the stalebot keeps coming back to deep-sitting bugs that we'll pretty much never fix accidentally / in passing, now we're automating it: the stalebot will lay off the bugs that have already gone through the cycle of “reported — stalebot asks to confirm — the users confirm” once.
This might need to be complemented with a yearly sweep of the
never staleissues as a sanity check, but first we just shed the manual work.Release Notes: