-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Move self-check use case to "more" section #9137
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
why move the docs? they won't render if in experimental |
This is a good point. These were more "notebooks" than clearly fleshed out "use-cases", so they should not be in "use-cases" imo. However, I think I agree w/ keeping them as render-able docs. Let me find a better place to put them in docs (outside of use-cases). The same will go for code-writing and agents. |
a5306b9
to
076d520
Compare
Note: discussed w/ @baskaryan and we'll move these back to use cases but under a tab that collects more experimental use cases (agents, code gen, etc). |
Co-authored-by: Bagatur <baskaryan@gmail.com>
No description provided.