@joseph0007 can you please fix the commit message? See https://github.com/nodejs/node/blob/main/doc/contributing/pull-requests.md#commit-message-guidelines.

Could you lint the first commit? You can use npx core-validate-commit

Ok will change the commit message in a bit.

I won't be able to change the commit message, it will have to be done by someone with access.

Here's how I fixed it:

git fetch https://github.com/nodejs/node.git main
git reset FETCH_HEAD --hard
curl -L https://github.com/nodejs/node/pull/50370.patch | git am
# here I changed `open` to `start` as suggested in the comment above
git commit --amend -m 'doc: add missing word in `child_process.md`'
git push git@github.com:joseph0007/node.git HEAD:patch-1 -f

CI: https://ci.nodejs.org/job/node-test-pull-request/56702/

@mcollina Please refrain from starting Jenkins CI on doc-only PR, it's not required and a waste of time (both for Jenkins hosts, and volunteers who can't use the CQ while the Jenkins result is pending).

Landed in fa95289

That is the only way to land PRs using the commit queue. I’ll refrain from starting it and landing docs PRs from now on. (I do not have time to manually land them, as I mostly do these light reviews from mobile).

That is the only way to land PRs using the commit queue

This is not correct AFAIK, the CQ is perfectly able to land doc-only PR without Jenkins CI, e.g. see it in action in #51374 or #51184

Ah my mistake. At some point it wasn’t. I’ll try it next time.