-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Nominating @geeksilva97 to be a collaborator #57032
Labels
meta
Issues and PRs related to the general management of the project.
Comments
+1 |
Thank you for the nomination. A great honor for me! |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
They have been contributing consistently for a while now. Being able to run the CI would be helpful and I think they have enough commits and involvement in the Node.js repos to warrant a collaborator nomination.
Commits authored on nodejs/node: github.com/nodejs/node/commits?author=geeksilva97
Pull requests opened: github.com/search?q=author:geeksilva97+org:nodejs&type=pullrequests
Issues opened: github.com/search?q=author:geeksilva97+org:nodejs&type=issues
Comments on pull requests and issues throughout the Node.js organization: https://github.com/search?q=commenter%3Ageeksilva97+org%3Anodejs&type=pullrequests
Private nomination (visible to collaborators only): https://github.com/nodejs/collaborators/discussions/218
cc: @geeksilva97 @nodejs/collaborators
The text was updated successfully, but these errors were encountered: