-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[DOCS] Change href from relative path to root in API docs (version 0.18) #10507
Conversation
✅ Deploy Preview for niobium-lead-7998 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## develop #10507 +/- ##
===========================================
+ Coverage 80.10% 80.13% +0.03%
===========================================
Files 461 461
Lines 39979 39978 -1
===========================================
+ Hits 32024 32037 +13
+ Misses 7955 7941 -14 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…ce to page section)
…nificantly other external link)
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.
I manually reviewed several links in the deploy build but there are too many. Please merge and manually test to confirm everything is working.
Jira Ticket
Deploy Preview
Description
Changed every dinamically generated path in an href in the API version 0.18 ( example:
href="../../checkpoint/Checkpoint_class"
tohref="/https/github.com/docs/0.18/reference/api/checkpoint/Checkpoint_class"
)invoke lint
(usesruff format
+ruff check
)For more information about contributing, see Contribute.
After you submit your PR, keep the page open and monitor the statuses of the various checks made by our continuous integration process at the bottom of the page. Please fix any issues that come up and reach out on Slack if you need help. Thanks for contributing!