-
Notifications
You must be signed in to change notification settings - Fork 556
Document rustdoc frontend CI checks #2562
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
Conversation
Thanks for the PR. If you have write access, feel free to merge this PR if it does not need reviews. You can request a review using r? rustc-dev-guide
or r? <username>
.
r? rustc-dev-guide
this seems ok to me.
@GuillaumeGomez @jsha do you have time to review this?
Please don't put it into the GUI test suite file, it's specifically for tests/rustdoc-gui/
, nothing else. Please keep the separation. This doesn't belong there.
Thanks for the feedback. I've moved the content out of the GUI test suite file and into the main rustdoc.md file instead. Also updated the command to use ./x.py test tidy --extra-checks=js and removed the manual linter instructions as suggested.
This comment has been minimized.
This comment has been minimized.
a17f345
to
91f915d
Compare
91f915d
to
0380c32
Compare
Thanks, @lolbinarycat — I updated the patch per your notes
Uh oh!
There was an error while loading. Please reload this page.
Adds a section to the rustdoc overview explaining that ESLint and TypeScript checks run through tidy in CI, not compiletest. Includes the command to run these checks locally.
This helps contributors understand why their local rustdoc tests might pass but CI fails on frontend linting.
Addresses #2364.