|
|
|
|
|
by patrickdevivo
2338 days ago
|
|
I think this is an awesome idea, and I would totally use it. I do agree with some of the comments about the added weight of slack where possibly just an email could suffice. Or at least having the ability to tweak how I'm notified with a custom webhook option. I think the value proposition is solid for just anyone on a team working in a medium-large sized codebase, where for some period of time, one person may only really be interested in changes to source in one particular subdirectory or file. It might be silly, but I wonder if there could be value in the inverse of this - alert me when a file or certain parts of a codebase have not been updated in some time (6 months+ say). It could be a good indicator that maybe a feature/section of code ought to be reviewed again. Maybe even have the notification be based on the average time between changes in other files, not necessarily absolute timeframes. |
|