chore: auto-close stale "waiting for info" items with Carson's no-response-closer - #10585
Open
paulbalandan wants to merge 1 commit into
Open
paulbalandan wants to merge 1 commit into
paulbalandan wants to merge 1 commit into
Conversation
paulbalandan
force-pushed
the
carson-waiting-for-info
branch
from
September 25, 2026 08:47
14e1708 to
46fcff2
Compare
This branch has not been deployed
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.
Description
Adds a second
no-response-closerrule so items labelledwaiting for infoare closed automatically when the author stops responding, and bumps Carson to v1.7.0 for the option that makes this safe.The label is used on both issues and PRs: 68 closed issues and 30 closed PRs carry it, and 27 of those PRs were closed unmerged, by hand, after the author went quiet. This takes over that chore.
How it behaves:
waiting for info. The item then drops out of the sweep, so an answered item is never closed for lack of a response.The
needs templaterule is unchanged and does not useunlabel_on_response.template-enforceralready removes that label once the description complies, and a comment should not rescue an issue that still skips the template.Checklist: