docs: update stale models docs link in generated config#12943
Open
minh2416294 wants to merge 1 commit into
Open
docs: update stale models docs link in generated config#12943minh2416294 wants to merge 1 commit into
minh2416294 wants to merge 1 commit into
Conversation
The example config written by the create-new-assistant flow linked to docs.continue.dev/customization/models, which now only resolves via a redirect. Point it at the canonical /customize/models path. Fixes continuedev#12669
Author
|
I have read the CLA Document and I hereby sign the CLA |
Author
|
fyi the red checks aren't from this pr. its a one line docs comment change in core/config. jetbrains-tests and the win32 vsix build are red on the other open prs too (#12940-12942) so seems like pre-existing ci flakiness, not this. core-checks / lint / prettier / test matrix / cla all green. |
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
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.
What
Updates the docs link in the generated example config from
https://docs.continue.dev/customization/modelstohttps://docs.continue.dev/customize/modelsWhy
The "create new assistant" flow (
core/config/createNewAssistantFile.ts)writes an example
config.yamlfor new users. Its "Define which models canbe used" comment links to
/customization/models, which is no longer acanonical page. It only resolves through the redirect defined in
docs/docs.json(/customization/models→/customize/models). New usersfollowing the link are bounced through a redirect. This points them straight
at the live page.
How
One-line change to the
DEFAULT_ASSISTANT_FILEtemplate comment.Testing
No tests. This is a comment-only string change inside a config template;
there's no behavioral assertion tied to the URL, and the file's formatting is
unchanged (comment text only). Verified locally:
git diff --checkclean,Prettier-neutral (only the URL text changed, no structural edits).
Fixes #12669