-
Notifications
You must be signed in to change notification settings - Fork 29.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
test: replace foreach with for #50599
Conversation
Can you please revert unrelated changes? |
Done |
@lpinca what happened? Looks like the merge is still blocked. Just trying to understand how nodejs CI system actually works. |
Unrelated CI failure. |
@bluescreen can you please also change "replaced" to "replace" in the commit message? We can do that before landing but it would be easier if you do it as we can simply apply the "commit-queue" label and get the PR merged automatically in that case. Thank you. |
I squashed the commits and changed the message. Now only the relevant changes made on nodeconf should be in the PR. Hope it's fine for a first learning contribution in nodejs. :) |
@lpinca what went wrong? |
Wohoo it worked! All checks passed. Ready to merge :) |
Thank you @bluescreen! |
Landed in ff879cd |
PR-URL: #50599 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: nodejs#50599 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: #50599 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
PR-URL: #50599 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
nodeconf 2023