Skip to content
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

[2.3.0][Tune][Doc] Restructure API reference #32449

Merged
merged 3 commits into from
Feb 13, 2023

Conversation

justinvyu
Copy link
Contributor

Why are these changes needed?

Cherry pick of #32311 and #32442 (fixed link check errors from the 1st PR).

This PR splits up long API refs into individual pages, one dedicated to each method/class. There are now 3 layers: an index page (ex: doc/tune/api/api.rst), a summary page for each group of APIs (ex: doc/tune/api/trainable.rst), and an individual page for each API (ex: doc/tune/api/docs/tune.Trainable.rst).

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@cadedaniel
Copy link
Member

Thanks @justinvyu ! Let's wait until #32446 is merged.

@cadedaniel
Copy link
Member

Ready for approval @zhe-thoughts. Not blocking the release test run today.

@@ -119,6 +119,7 @@ scripts/nodes.txt
/doc/_build
/doc/source/_static/thumbs
/doc/source/tune/generated_guides/
/doc/source/**/doc/
Copy link
Member

Choose a reason for hiding this comment

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

@justinvyu can you explain why this is necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We now have autogenerated API files under /doc/source/tune/api/doc/*, /doc/source/data/api/doc/*, etc. We shouldn't track these with git.

@justinvyu
Copy link
Contributor Author

Note: I had to make another commit removing a reference to an API that has landed in master but not 2.3.0.

@cadedaniel
Copy link
Member

cc @zhe-thoughts merging this doc change in now

@cadedaniel cadedaniel merged commit 184efec into ray-project:releases/2.3.0 Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants