FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

doc: fix hardwareConcurrency example by tniessen · Pull Request #50278 · nodejs/node · GitHub

/ node Public

doc: fix hardwareConcurrency example - #50278

Merged
aduh95 merged 1 commit into
nodejs:mainfrom
tniessen:navigator-is-bad
Oct 23, 2023
Merged

doc: fix hardwareConcurrency example#50278
aduh95 merged 1 commit into
nodejs:mainfrom
tniessen:navigator-is-bad

Conversation

Copy link
Copy Markdown
Member

Refs: #47769

tniessen added doc Issues and PRs related to the documentations. experimental Issues and PRs related to experimental features. labels Oct 19, 2023
tniessen added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Oct 19, 2023
H4ad added the request-ci Add this label to start a Jenkins CI on a PR. label Oct 19, 2023
github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Oct 19, 2023

Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Collaborator

Uzlopak left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

LGTM

Copy link
Copy Markdown
Member Author

@H4ad This PR did not need a Jenkins CI run because it touches documentation only.

H4ad commented Oct 19, 2023
edited
Loading

Copy link
Copy Markdown
Member

@tniessen Oh, thanks for letting me know.

In cases like this, should we just fast-track or there is another behavior?

tniessen commented Oct 19, 2023
edited
Loading

Copy link
Copy Markdown
Member Author

In cases like this, should we just fast-track or there is another behavior?

Any collaborator may suggest fast-tracking of such small doc-only changes by adding the fast-track label. But it's perfectly reasonable for a PR like this to wait for two days to land (without Jenkins CI) since it's not urgent by any means.


IIRC, now that Jenkins CI has been started, we have to run it until it passes for the commit queue to not reject the PR, but perhaps I am misremembering or things have changed.

Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Collaborator

Copy link
Copy Markdown
Member Author

Not sure what's going on with ARM...

aduh95 merged commit fa514c9 into nodejs:main Oct 23, 2023

aduh95 commented Oct 23, 2023

Copy link
Copy Markdown
Contributor

Landed in 5d33203

targos pushed a commit that referenced this pull request Oct 24, 2023
PR-URL: #50278
Refs: #47769
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Vinícius Lourenço Claro Cardoso <contact@viniciusl.com.br>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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 outstanding review comments, and a CI started. doc Issues and PRs related to the documentations. experimental Issues and PRs related to experimental features.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants


Back | FazBrowse Home | New Git URL