-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
[v20.x backport] watch: fix arguments parsing #53162
[v20.x backport] watch: fix arguments parsing #53162
Conversation
PR-URL: nodejs#52760 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Raz Luvaton <rluvaton@gmail.com>
I would not assume #52760 needs manual backporting without @nodejs/releasers requesting for it |
Hi @MoLow I think this commit should fix a regression which was introduced in
Do you mean the fix will be automatically back-ported into |
yes, that is usually how backporting is done. manual backporting is needed only in case there are conflicts/CI fails etc |
Oh thanks a lot! Shall I close this PR instead? If so I will leave a comment under #53102 to explain that the fix shall be back ported by the nodejs/releasers team. |
lets wait for an answer from @nodejs/releasers |
07c45ba
to
e6d9fbe
Compare
usually it needs to stay 2 weeks in the current in order to be able to be backported (if the original commit does not land cleanly) |
Thanks @marco-ippolito! Does that mean I can close this PR and wait for the backport? |
Id say keep it open until it the original gets released, if doesnt land cleanly we have the backport ready |
Closing as the original commit lands cleanly 739adf90b1 |
Fixes: #53102
PR-URL: #52760
Reviewed-By: Benjamin Gruenbaum benjamingr@gmail.com
Reviewed-By: Raz Luvaton rluvaton@gmail.com