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

Update child_process.md #50370

Merged
merged 1 commit into from
Jan 7, 2024
Merged

Update child_process.md #50370

merged 1 commit into from
Jan 7, 2024

Conversation

joseph0007
Copy link
Contributor

@joseph0007 joseph0007 commented Oct 24, 2023

child_process: grammatical issue was fixed with the sentence.

@nodejs-github-bot nodejs-github-bot added child_process Issues and PRs related to the child_process subsystem. doc Issues and PRs related to the documentations. labels Oct 24, 2023
@@ -842,7 +842,7 @@ pipes between the parent and child. The value is one of the following:
file, socket, or a pipe with the child process. The stream's underlying
file descriptor is duplicated in the child process to the fd that
corresponds to the index in the `stdio` array. The stream must have an
underlying descriptor (file streams do not until the `'open'` event has
underlying descriptor (file streams do not open until the `'open'` event has
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if "open" is the correct term here, maybe "start"? @nodejs/streams @nodejs/child_process wdyt?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a native speaker but "start" seems better. However, I think "open" is fine too.

@@ -842,7 +842,7 @@ pipes between the parent and child. The value is one of the following:
file, socket, or a pipe with the child process. The stream's underlying
file descriptor is duplicated in the child process to the fd that
corresponds to the index in the `stdio` array. The stream must have an
underlying descriptor (file streams do not until the `'open'` event has
underlying descriptor (file streams do not open until the `'open'` event has
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a native speaker but "start" seems better. However, I think "open" is fine too.

@lpinca
Copy link
Member

lpinca commented Oct 27, 2023

@mcollina
Copy link
Member

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

@joseph0007
Copy link
Contributor Author

Ok will change the commit message in a bit.

@joseph0007
Copy link
Contributor Author

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

@aduh95
Copy link
Contributor

aduh95 commented Jan 6, 2024

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 [email protected]:joseph0007/node.git HEAD:patch-1 -f

@aduh95 aduh95 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jan 6, 2024
@mcollina mcollina added the request-ci Add this label to start a Jenkins CI on a PR. label Jan 7, 2024
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jan 7, 2024
@nodejs-github-bot
Copy link
Collaborator

@aduh95
Copy link
Contributor

aduh95 commented Jan 7, 2024

@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).

@aduh95 aduh95 merged commit fa95289 into nodejs:main Jan 7, 2024
44 of 47 checks passed
@aduh95
Copy link
Contributor

aduh95 commented Jan 7, 2024

Landed in fa95289

@mcollina
Copy link
Member

mcollina commented Jan 7, 2024

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).

@aduh95
Copy link
Contributor

aduh95 commented Jan 7, 2024

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

@mcollina
Copy link
Member

mcollina commented Jan 7, 2024

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

marco-ippolito pushed a commit to marco-ippolito/node that referenced this pull request Jan 12, 2024
PR-URL: nodejs#50370
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Zeyu "Alex" Yang <[email protected]>
Medhansh404 pushed a commit to Medhansh404/node that referenced this pull request Jan 19, 2024
PR-URL: nodejs#50370
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Zeyu "Alex" Yang <[email protected]>
targos pushed a commit that referenced this pull request Feb 15, 2024
PR-URL: #50370
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Zeyu "Alex" Yang <[email protected]>
@marco-ippolito marco-ippolito mentioned this pull request Mar 1, 2024
richardlau pushed a commit that referenced this pull request Mar 25, 2024
PR-URL: #50370
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Zeyu "Alex" Yang <[email protected]>
richardlau pushed a commit that referenced this pull request Mar 25, 2024
PR-URL: #50370
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Zeyu "Alex" Yang <[email protected]>
@richardlau richardlau mentioned this pull request Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. child_process Issues and PRs related to the child_process subsystem. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants