-
Notifications
You must be signed in to change notification settings - Fork 30k
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
doc: add jdalton to collaborators #20968
Conversation
Welcome :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome!
Thank you! (I currently still need the bits toggled to be able to spin up a CI run and-or merge). |
README.md
Outdated
@@ -393,6 +393,8 @@ For more information about the governance of the Node.js project, see | |||
* [jasongin](https://github.com/jasongin) - | |||
**Jason Ginchereau** <jasongin@microsoft.com> | |||
* [jbergstroem](https://github.com/jbergstroem) - | |||
**John-David Dalton** <john.david.dalton@gmail.com> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jdalton Are you being onboarded by somebody at the moment? We usually open these PRs as part of that process – not that there’s anything wrong with this PR, but I think we want to wait with merging it until that occurs? |
@addaleax I thought these PRs are always meant to be merged by the onboarded person. If there was no onboarding, that is of course not happening. |
That's cool. No one has contacted me yet for onboarding (so I figured I'd get the ball rolling). |
I'm going to set blocked just to prevent anyone else merging (although by convention these PRs should only be merged by the onboarded person anyway). Obviously consider it unblocked when the onboarding occurs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Landed in bb6b605 |
PR-URL: nodejs#20968 Fixes: nodejs#20828 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Yuta Hiroto <hello@hiroppy.me> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Shingo Inoue <leko.noor@gmail.com>
post-closure LGTM! |
Welcome aboard @jdalton ! |
PR-URL: #20968 Fixes: #20828 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com> Reviewed-By: Ali Ijaz Sheikh <ofrobots@google.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Yuta Hiroto <hello@hiroppy.me> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Shingo Inoue <leko.noor@gmail.com>
Fixes: #20828
Checklist