-
Notifications
You must be signed in to change notification settings - Fork 212
Feature request: Ignore issues written by a particular author #173
Comments
Same! I opened #172 to resolve this, which adds a bit of flexibility by using the assignee rather than the original author (which allows issues to be transferred). Do you think this would fulfill your feature request, or is it important that issues follow the original author? |
@christianbundy I looked at #172 and just want to make sure I understand -- does this mean that if the issue is assigned to someone it cannot be marked as stale? Its not exactly what I had in mind but would be very helpful too! |
Yep, exactly. The two benefits are:
|
Great! Thanks for adding this. I look forward to when it gets merged! |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
@christianbundy is this feature available yet? I'd love to add it to my implementation of stalebot. Thanks, please let me know! |
Yep, it's used like this: # Set to true to ignore issues with an assignee (defaults to false)
exemptAssignees: true As long as there's an assignee the issue will be kept safe from stale[bot]. |
Thanks @christianbundy! Using this feature now, it is much appreciated! |
As a developer on my project, I sometimes use issues as a sort of to-do list. It would be great if I could ignore my own or my teammates' issues when determining what is stale. Something like an "exemptAuthors" array would be cool.
The text was updated successfully, but these errors were encountered: