Repository navigation
📝 docs: Add Conversation Pull Requests Documentation - #808
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📦 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! 🙌 |
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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e090c339a7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "agents_api", | ||
| "artifacts", | ||
| "code_interpreter", | ||
| "pull_requests", |
There was a problem hiding this comment.
Keep the gated page out of navigation
If this commit is merged before LibreChat#16876 and the unresolved workspace-repository setup requirement are completed, this entry makes the page publicly discoverable even though the page's own publishing gate explicitly says not to publish it yet. Users can consequently follow examples that depend on unsupported default-on, token-fallback, and allowAllRepositories behavior; defer this navigation entry and the associated cross-links until those prerequisites land and the pending guidance is reverified.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Agreed that the page must not go live early, which is why the PR body says not to merge until LibreChat#16876 lands and the page opens with a publishing-gate comment. Keeping the nav entry in this PR lets the page be reviewed in the built site, and removing it is a one-line change. Leaving this open for the maintainer to decide whether to drop the entry or hold the merge.
📦 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! 🙌 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a15cd1e0fb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
📦 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! 🙌 |
Summary
Documents conversation pull requests: the chat header chip, sidebar mark and card that show a chat's GitHub pull request when it runs code in an attached workspace.
features/pull_requests(requirements, setup, what users see, matching, behavior, security, troubleshooting, API reference), added to the Features nav.pullRequestssection underendpoints.agentsin the Agents object structure reference, with the 14 documented keys; defaults and ranges checked againstconfigSchemaondev.dotenv(the token variable,CODEAPI_BRIDGE_LANE_GIT) and a cross-link from the Code Interpreter page.GitPullRequesticon inlib/icons.tsxso the new page shows its sidebar icon.This documents only what is on
devtoday:enabled: true, a${NAME}token reference andallowedRepositories. The default-on behavior, token environment fallback andallowAllRepositoriesfrom LibreChat-AI/LibreChat#16876 are left out until that PR merges, then they can be added in a follow-up.Open items, left as TODO comments in the page rather than guessed:
Testing
pnpm typecheck,pnpm lint,pnpm test(404 tests) andprettier --checkon the changed files all exit 0..mdxfiles compile with@mdx-js/mdxandremark-gfm.pnpm build(exceeded the 300 s limit) and rendering in a browser. Dev-server requests for docs pages failed withERR_STRING_TOO_LONG, including pages this PR does not touch.