Skip to content
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

Conversation

jakecastelli
Copy link
Contributor

Fixes: #53102

PR-URL: #52760
Reviewed-By: Benjamin Gruenbaum benjamingr@gmail.com
Reviewed-By: Raz Luvaton rluvaton@gmail.com

PR-URL: nodejs#52760
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Raz Luvaton <rluvaton@gmail.com>
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. v20.x v20.x Issues that can be reproduced on v20.x or PRs targeting the v20.x-staging branch. labels May 26, 2024
@MoLow
Copy link
Member

MoLow commented May 26, 2024

I would not assume #52760 needs manual backporting without @nodejs/releasers requesting for it

@MoLow MoLow changed the title watch: fix arguments parsing [v20.x backport] watch: fix arguments parsing May 26, 2024
@jakecastelli
Copy link
Contributor Author

jakecastelli commented May 26, 2024

Hi @MoLow I think this commit should fix a regression which was introduced in v20.13.0.

I would not assume #52760 needs manual backporting without @nodejs/releasers requesting for it

Do you mean the fix will be automatically back-ported into v20.x? Sorry, I didn't quite get it, do you mind elaborate a bit more?

@MoLow
Copy link
Member

MoLow commented May 26, 2024

Do you mean the fix will be automatically back-ported into v20.x? Sorry, I didn't quite get it, do you mind elaborate a bit more?

yes, that is usually how backporting is done. manual backporting is needed only in case there are conflicts/CI fails etc

@jakecastelli
Copy link
Contributor Author

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.

@MoLow
Copy link
Member

MoLow commented May 26, 2024

lets wait for an answer from @nodejs/releasers

@jakecastelli jakecastelli changed the base branch from v20.x to v20.x-staging May 26, 2024 14:59
@marco-ippolito
Copy link
Member

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)

@jakecastelli
Copy link
Contributor Author

Thanks @marco-ippolito! Does that mean I can close this PR and wait for the backport?

@marco-ippolito
Copy link
Member

Id say keep it open until it the original gets released, if doesnt land cleanly we have the backport ready

@marco-ippolito
Copy link
Member

Closing as the original commit lands cleanly 739adf90b1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ci PRs that need a full CI run. v20.x v20.x Issues that can be reproduced on v20.x or PRs targeting the v20.x-staging branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants