-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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 @daeyeon as a collaborator #44142
Labels
meta
Issues and PRs related to the general management of the project.
Comments
RaisinTen
added
the
meta
Issues and PRs related to the general management of the project.
label
Aug 5, 2022
+1! |
welcome onboard! @daeyeon |
I'm deeply honored. Thanks for nominating me! |
Welcome @daeyeon ! |
Fyko
pushed a commit
to Fyko/node
that referenced
this issue
Sep 15, 2022
Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com PR-URL: nodejs#44355 Fixes: nodejs#44142 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Kohei Ueno <kohei.ueno119@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com PR-URL: nodejs/node#44355 Fixes: nodejs/node#44142 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Kohei Ueno <kohei.ueno119@gmail.com>
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Jan 3, 2023
Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com PR-URL: nodejs/node#44355 Fixes: nodejs/node#44142 Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Kohei Ueno <kohei.ueno119@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I would like to nominate @daeyeon as a collaborator. They've been an active contributor in a variety of areas in Node.js recently, notably as a triagger, so I think they would be a valuable addition to the team!
Here is a summary of their contributions:
Pull requests and issues opened throughout the Node.js organization: https://github.com/search?q=author:daeyeon+org:nodejs
Commits in nodejs/node: https://github.com/nodejs/node/commits?author=daeyeon
Pull requests and issues in nodejs/node: https://github.com/nodejs/node/issues?q=author:daeyeon
Comments on pull requests and issues in nodejs/node: https://github.com/nodejs/node/issues?q=commenter:daeyeon
Reviews on pull requests in nodejs/node: https://github.com/nodejs/node/pulls?q=reviewed-by:daeyeon
Help provided to end-users and novice contributors: https://github.com/nodejs/help/issues?q=commenter:daeyeon
Pull requests and issues opened throughout the Node.js organization:
https://github.com/search?q=author:daeyeon+org:nodejs
Comments on pull requests and issues throughout the Node.js organization: https://github.com/search?q=commenter:daeyeon+org:nodejs
//cc @nodejs/collaborators
The text was updated successfully, but these errors were encountered: