-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
doc: document the benchmark CI #16086
Conversation
### Running Benchmarks on the CI | ||
|
||
To see the performance impact of a Pull Request by running benchmarks on | ||
the CI, check out [How to: Running core benchmarks on Node.js CI](benchmark-ci). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link is 404. [How to: Running core benchmarks on Node.js CI][benchmark-ci]
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo @vsemozhetbyt 's nit
aa4c9f2
to
6a889c5
Compare
Landed in 0a64a6a with @vsemozhetbyt's nits fixed. Thanks! |
PR-URL: #16086 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
PR-URL: #16086 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
PR-URL: nodejs/node#16086 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
I don't think this is up to date for v6.x. Please lmk if I am mistaken |
Checklist
Affected core subsystem(s)
doc