New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Give Triagers access to the Node.js feature requests project #861
Comments
SGTM. I created that project and I don't think anyone's been maintaining it recently. |
If we have access, I'd gladly reorganize it (nodejs/node#52485). I really like it's concept, but it just needs a bit of oversight. |
+1 |
Great! I'll close this issue once we get access (or a different conclusion is reached) Thanks for your help! |
I'm glad we are a fan of this idea, I'm exciting to help out :-) |
Do you think it'll also be a good idea to create a Node.js bug reports project? I'm happy to manage it if needed |
What would you do with it? |
I meant just for tracking issues so that they are known |
/cc @nodejs/tsc |
(CC @nodejs/issue-triage)
As a (relatively new) member of the Issue Triage team, I think it'd be reasonably helpful if we had the permissions to move issues around in the Node.js feature requests project. This way, we can mark issues as triaged/stale/fixed rather than waiting for the bot to mark them stale or an admin to change their status.
The text was updated successfully, but these errors were encountered: