[Doc] Fix bad doc and recover doc of c++ api#22213
Merged
raulchen merged 1 commit intoray-project:masterfrom Feb 8, 2022
Merged
[Doc] Fix bad doc and recover doc of c++ api#22213raulchen merged 1 commit intoray-project:masterfrom
raulchen merged 1 commit intoray-project:masterfrom
Conversation
Contributor
Author
raulchen
approved these changes
Feb 8, 2022
Contributor
|
@SongGuyang my mistake, was not intentional. |
Contributor
Author
|
@maxpumperla Don't worried. Please give notice to the PR author if you don't ensure next time. |
maxpumperla
pushed a commit
that referenced
this pull request
Feb 16, 2022
ericl
added a commit
that referenced
this pull request
Feb 17, 2022
* [docs] landing page (fixes #21750) (#21859) Co-authored-by: Richard Liaw <rliaw@berkeley.edu> * [Doc] Fix bad doc and recover doc of c++ api (#22213) * [Docs] Ray Data docs target state (#21931) Preview: [docs](https://ray--21931.org.readthedocs.build/en/21931/data/dataset.html) The Ray Data project's docs now have a clearer structure and have partly been rewritten/modified. In particular we have - [x] A Getting Started Guide - [x] An explicit User / How-To Guide - [x] A dedicated Key Concepts page - [x] A consistent naming convention in `Ray Data` whenever is is referred to the project. This surfaces quite clearly that, apart from the "Getting Started" sections, we really only have one real example. Once we have more, we can create an "Example" section like many other sub-projects have. This will be addressed in #21838. * [Datasets] [Docs] Datasets library branding + positioning tweaks (#22067) * [train] Minor fixes on Ray Train user guide doc (#22379) Fixes some typos and format issues. * [Doc] Fix bad links of dask and mars in ray-libraries.rst (#22210) * merge Signed-off-by: Max Pumperla <max.pumperla@googlemail.com> * merge Signed-off-by: Max Pumperla <max.pumperla@googlemail.com> * merge Signed-off-by: Max Pumperla <max.pumperla@googlemail.com> * [docs] Clean up long titles in TOC (#22016) * LINT Signed-off-by: Max Pumperla <max.pumperla@googlemail.com> Co-authored-by: Richard Liaw <rliaw@berkeley.edu> Co-authored-by: Guyang Song <guyang.sgy@antfin.com> Co-authored-by: Clark Zinzow <clarkzinzow@gmail.com> Co-authored-by: Hao Chen <chenh1024@gmail.com> Co-authored-by: Eric Liang <ekhliang@gmail.com>
simonsays1980
pushed a commit
to simonsays1980/ray
that referenced
this pull request
Feb 27, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
copied from v1.10.0 https://docs.ray.io/en/latest/#getting-started-with-ray
Related issue number
Checks
scripts/format.shto lint the changes in this PR.