Fix staleness comments to suppress owner pings when tooManyOwners #1219
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.
makeStaleness()was unconditionally passing the full owner list to comment generators, causing staleness comments to ping 50+ owners when thetooManyOwnersflag was set.Changes
getStaleness()to checktooManyOwnersbefore populatingownersToPing["«maintainers»"]instead of the full owner list@«maintainers»in comments—clear but non-pingingThis follows the existing pattern for the "no owners" case, which uses
["«anyone?»"].Example
Before (with 60 owners):
After:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.