repomountie assigning many/all users to bot issues

[stephhazlitt]

When {repomountie} bot opens a poke issue it sometimes assigns multiple (or even all) contributors to the issue, and it appears to sometimes assign team members that that are associated with the repo but who have never contributed code the repo? This of course fills contributors/team members GitHub notification boxes with extraneous notifications and if a contributor does decides to close the issue, they can learn after spending time clicking through that the issue was already closed by one of the other assignees. This feels unnecessarily noisy and inefficient, especially for teams with many, many repos.

Example: bcgov/WES-results-visualization#8 (comment)

Definition of done
{repomountie} assigns only one Assignee, who is either recently active (best), has contributed code at some point (ok) or does not assign, but does not assign users from the associated teams.

[repo-mountie]

Its often hard for people to acknowledge that some things are just not that important and, unfortunately, some issues will never get done - like this issue for example; Its been stagnant for 90 days. For me, being a robot, I'm happy to face the facts and, as a result, I'm closing this issue.

Pro Tip

• If you're sad and want to re-open this issue you'll have another 90 days to address it.

• Or, if you want me to ignore this issue and never close it again, add the label "neverstale".

[stephhazlitt]

This is Issue is still not resolved :(