Direct stale PRs to core-dev channel #25302
Merged
Conversation
This file contains 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
wendigo
approved these changes
Mar 13, 2025
dain
approved these changes
Mar 14, 2025
mosabua
changed the title
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.
Description
I wont have the bandwidth to handhold all stale PRs anymore. If anyone else could be taking up that job we can add that person but for now I think we can just send people to #core-dev and expand the time to stale and the time to close. What do you all think?
After discussion on slack and different ideas around the timing and workflow I am leaving it unchanged for now. We can figure out next steps separately. The current PR only removes the noise of notifications for me.
Additional context and related issues
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.