Skip to content

Conversation

Copy link

Copilot AI commented Nov 18, 2025

makeStaleness() was unconditionally passing the full owner list to comment generators, causing staleness comments to ping 50+ owners when the tooManyOwners flag was set.

Changes

  • Modified getStaleness() to check tooManyOwners before populating ownersToPing
  • When true, passes placeholder ["«maintainers»"] instead of the full owner list
  • Placeholder renders as @«maintainers» in comments—clear but non-pinging

This follows the existing pattern for the "no owners" case, which uses ["«anyone?»"].

Example

Before (with 60 owners):

Re-ping @user1, @user2, @user3, ... @user60:

After:

Re-ping @«maintainers»:
Original prompt

This section details on the original issue you should resolve

<issue_title>mergebot staleness comments do not respect tooManyOwners</issue_title>
<issue_description>makeStaleness() unconditionally slings the owner list to the comment generator – it should be suppressing this output if too many owners.</issue_description>

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

When there are too many owners (>50), use a placeholder "@«maintainers»"
instead of listing all owners in staleness comments to avoid spam.

Co-authored-by: jakebailey <[email protected]>
Copilot AI changed the title [WIP] Fix staleness comments to respect tooManyOwners Fix staleness comments to suppress owner pings when tooManyOwners Nov 18, 2025
Copilot AI requested a review from jakebailey November 18, 2025 19:54
Copilot finished work on behalf of jakebailey November 18, 2025 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

mergebot staleness comments do not respect tooManyOwners

2 participants