-
Notifications
You must be signed in to change notification settings - Fork 346
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
feat: 🎸 new api overview #1527
base: main
Are you sure you want to change the base?
feat: 🎸 new api overview #1527
Conversation
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.
LGTM
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.
LGTM
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.
LGTM
Thanks for improving this doc page!
@hcfw007 this PR needs one more approval to trigger the auto-merge, which I had set a long time ago. Please get your PR merged. Thanks! |
According to our previous discussion, we should review this new doc chapter by chatper. So I'm working to get the seconder chapter pushed. However I'm trying to solve a. prolem preventing me from clone the repo. |
Head branch was pushed to by a user without write access
@huan I solved the newtwork problem. Now the second section is ready to be reviewed. |
I don't think the Can you remove it? Or please explain why it can be put under this folder, according to the |
As we agreed in this PR #1525 (comment)
New doc will be pushed section by section. The next section will only be pushed if the previous one is approved.
And after all sections are pushed and approved, this PR will be merged.