-
Notifications
You must be signed in to change notification settings - Fork 561
Feature Request: Documentation versioning #45
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
Comments
hey thanks!! yes, we plan to have versioning. |
Would be great if there was a way to tell context7 about which docs are "versioned" and which are directly from "main" we have the issue at serverpod/serverpod_docs that the repo contains the bleeding edge docs and versioned docs. This blows token count through the roof (counted 346,652 at context7.com) and like said above will probably result in hallucinations. Its a common pattern for docusaurus docs I believe. |
Awesome project 👏
Do you plan to support versioning?
For example, allowing NextJS 13 & 14 to help with working on “legacy” projects.
I guess it’s just about referencing a repository at a specific tag, like https://github.com/vercel/next.js/tree/v13.5.11 ?
The text was updated successfully, but these errors were encountered: