Skip to content

Stop stalebot from nagging on the same issues - #58418

Merged
zelenenka merged 1 commit into
mainfrom
zelenenka-no-comebacks-for-stalebot
Jun 3, 2026
Merged

Stop stalebot from nagging on the same issues#58418
zelenenka merged 1 commit into
mainfrom
zelenenka-no-comebacks-for-stalebot

Conversation

@zelenenka

Copy link
Copy Markdown
Contributor

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

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.
@cla-bot cla-bot Bot added the cla-signed The user has signed the Contributor License Agreement label Jun 3, 2026
@zed-community-bot zed-community-bot Bot added the staff Pull requests authored by a current member of Zed staff label Jun 3, 2026
@MrSubidubi MrSubidubi changed the title GitHub Actions: Stop stalebot from nagging on the same issues Stop stalebot from nagging on the same issues Jun 3, 2026
@zelenenka
zelenenka added this pull request to the merge queue Jun 3, 2026
Merged via the queue into main with commit 19b91c4 Jun 3, 2026
44 checks passed
@zelenenka
zelenenka deleted the zelenenka-no-comebacks-for-stalebot branch June 3, 2026 14:20
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 18, 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The user has signed the Contributor License Agreement staff Pull requests authored by a current member of Zed staff

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants