-
Notifications
You must be signed in to change notification settings - Fork 136
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
more subteams under Collaborators #537
Comments
+1 as long as this is a temporary solution. |
+1 |
2 similar comments
+1 |
+1 |
+1. If we're blocked on CODEOWNERS by subteams, perhaps it's worth investigating a more permanent solution - I think this is probably a valuable thing to have. |
FYI this might not be needed once we land nodejs/github-bot#265 (which should be soon) |
Done. Will be happy to undo it when the GitHub bot change lands. Until then, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Although I hope the need for subteams is only temporary, I've added
net
as a subteam and will addhttp2
once we remove non-collaborators from that team. (The non-collaborators are not active as far as I can tell.) That will enable us to use CODEOWNERS for http2 pull requests. Refs: nodejs/node#34534@nodejs/tsc @nodejs/community-committee
The text was updated successfully, but these errors were encountered: