Okay so first question, I noticed as soon as I looked at my notification page that it has a lot of notifications chilling from issues / prs that have been closed for days
wondering if it would make sense to automatically acknowledge issues / prs when they're closed
I think the current policy that we're trying to avoid heuristics entirely, pretty much. I think this one might work out in practice, but I would rather not do it.
is there a framework for working with the notifications that triagebot is using that we could use to implement custom handling for our personal notification set?
Not currently, no, if I understand you correctly. It's in theory plausible to run triagebot yourself, but it would need some modifications for sure (we currently depend on a webhook, and you AFAIK can't set up those yourself)
im probably abusing triagebot rn anyways, I don't really want it for notifications so much, though I do like that it makes that info public, so much as I want it to track inprogress work items
but for me the github notifications UI is completely sufficient for keeping track of my notifications, though I'm not dealing with nearly the volume that david and others are I'm sure
I think that's a separate, though very important, goal
if there are plans to start an active work tracker with triage bot as well I'd be very interested in being involved
I'm currently doing that with a github project board https://github.com/yaahc/prs/projects/1 but its painfully manual
fwiw, I think it would be very helpful if you wrote down (in an issue perhaps) your process and so forth
at least today part of the problem is that it's unclear which bits to automate
@simulacrum tada https://github.com/rust-lang/triagebot/issues/353
Thanks! I'll try to reply sometime soon.
no reply is really needed, but happy to hear feedback on various ideas I posted
yeah, I meant feedback / thoughts