Repository navigation
Review Requesting Comment #53897
Description
The triage team (including myself) constantly monitor this issue tracker, alongside other collaborators. Given this frequent monitoring, is the @nodejs-github-bot's automated comment request for teams to review issues really necessary?
The bot doesn't cover all source files, and subscribes all team members to all future updates for an issue. If specific individuals need to be notified about an issue, I believe this should be done manually. Since manual @ pings are already used for many source files, I don't think the bot comment is needed anymore.
There's no way to programatically tell who wants to be subscribed to what.
WDYT?
(Sorry for the noise regarding this in the other locations)
Activity
mhdawson commentedon Jul 18, 2024
Is there some problem that you are looking to solve with this? I don't think I've heard anybody complain about the bot comment requests.
avivkeller commentedon Jul 18, 2024
I was initially trying to move it to Github Actions, but there was discussion in nodejs/admin#895 and #53894 about removing it entirely, so I figured I'd open an issue
ovflowd commentedon Jul 19, 2024
Again, is there any particular issue this solves? Or is this just a different approach of what we already do today?
avivkeller commentedon Jul 19, 2024
I suppose you are correct, if it ain't broke don't fix it. I'll focus my attention of issues that more aftionsble.
ovflowd commentedon Jul 19, 2024
I also believe the current team organization is messy, but any overhaul is tricky and complicated.
But just changing how we do mentions won't fix the root issue, IMO.