-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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: fix broken references #6100
Conversation
/cc @nodejs/documentation I think we should consider some sort of docs CI that can build / host the docs. Reviewing a change like this would be much faster if all we had to do is click a link. |
LGTM and +1 to @thealphanerd's suggestion |
+1 |
PR-URL: #6100 Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in 3641ca9 |
PR-URL: #6100 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #6100 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #6100 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#6100 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #6100 Reviewed-By: James M Snell <jasnell@gmail.com>
If this is going to be backported I would like it to be done so manually to make sure we do not accidentally change information in the lts docs |
adding don't land for now. If anyone would like to backport please open a pull request targeting v4.x-staging |
Checklist
Affected core subsystem(s)
doc
Description of change
Fix multiple broken cross-references.