Repository navigation
Conversation
The endpoint examples were bare list items indented under keys that were never shown, so it was unclear where to paste them in librechat.yaml. Each snippet now includes the endpoints and custom keys, and the lead-in explains how to merge the entry into an existing custom list. Feedback: 1557760609578254458
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This branch was successfully deployed
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
1 participant
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.
Summary
The AI endpoint guides showed each
librechat.yamlexample as a bare- name:list item, indented four spaces under parent keys that were never shown. Readers could not tell where the snippet belonged, and pasting it at the top level produces invalid config. Every example on the 25 affected pages (31 snippets) now includes theendpoints:andcustom:keys. The intro sentence also explains that when anendpoints.customlist already exists, you paste only the- name:entry into it. The entries are unchanged: their existing indentation already matches the new parent keys. Azure and the section index were left alone because their examples already use a different, complete structure.Feedback addressed
1557760609578254458:/docs/configuration/librechat_yaml/ai_endpoints/deepseekValidation
librechat.yamlsnippet with PyYAML and assertedendpoints.customis a list with a named entry: 31 snippets, 0 failures@mdx-js/mdx: all compilednpx prettier --checkon the changed files: passedNot changed
1557474248656949386:/docs, a "good" rating with no message. No problem was reported, so nothing needs to change (NON-ACTIONABLE).