Repository navigation
Conversation
Extend the conversation pull request docs to the final feature: GitLab and Bitbucket Cloud providers, Enterprise and self-managed hosts, per-provider token fallbacks, YAML-only provider, host and oauth keys, per-user OAuth accounts, and the Redis shared cache. Drop the pending notes for the now merged default-on change.
|
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bfa5a1021a
ℹ️ 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".
| title: Conversation Pull Requests | ||
| icon: GitPullRequest | ||
| description: Show the GitHub pull request, size and CI status for chats that run code in an attached workspace. | ||
| description: Show the pull request or merge request, size and CI status for chats that run code in an attached workspace, on GitHub, GitLab or Bitbucket Cloud. |
There was a problem hiding this comment.
The frontmatter description is rendered independently in search results and documentation cards, where it advertises Bitbucket Cloud as currently supported even though this commit explicitly records Bitbucket support as pending on upstream PR #16987. The later (**Pending**) qualifier in the page body will not accompany that summary, so omit Bitbucket here or qualify it until the implementation ships.
Useful? React with 👍 / 👎.
| 3. The worker reports its branch. This needs a worker built from `LibreChat-AI/code-interpreter` PR #311 or later, and `CODEAPI_BRIDGE_LANE_GIT=true` set on the Code API. See [Code Interpreter](/docs/features/code_interpreter#attached-environments-and-pairing). | ||
|
|
||
| If a requirement is missing, chats simply show no pull request and no error is shown to the user. The exception is a `token` that is set but whose environment variable is empty or missing: lookups then fail with `NOT_CONFIGURED`, and sidebar rows show the warning icon with a retry button. | ||
| The feature is on by default. Without a token or a repository scope it stays dormant, and every chat simply shows no pull request, with no error. `enabled: false` turns it off whatever else is set. |
There was a problem hiding this comment.
When oauth is configured without a server token or repository scope, this sentence says the feature stays dormant, contradicting the newly documented behavior that a working OAuth app enables the feature by itself. Once the pending per-user-account support ships, this can lead administrators to add an unnecessary shared token; qualify the rule with the absence of a working OAuth app.
Useful? React with 👍 / 👎.
| | ------------------------------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | No chip and no sidebar mark anywhere | No token, no repository scope, or `enabled: false` | Check [Setup](#setup). Open `/api/config` while signed in and look for `pullRequestsEnabled: true`. | | ||
| | Header chip works, sidebar rows show nothing | `pullRequestsBatchVersion` is missing from `/api/config` (old build, or a stale tab) | Rebuild or upgrade the server, restart, and hard reload. Confirm `pullRequestsBatchVersion: 1`. | | ||
| | No chip for a chat in an attached workspace | The repository is not in `allowedRepositories` | Add it, or its owner as `owner/*`. A repository out of scope looks the same as one without a pull request. | |
There was a problem hiding this comment.
For a user with a connected OAuth account, allowedRepositories is deliberately ignored, so adding the repository or its owner as this row recommends cannot restore the missing chip. It may instead broaden the separate server token's access. Qualify this cause and fix as applying only to server-token lookups, and direct connected users to verify their account or app access.
Useful? React with 👍 / 👎.
📦 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
1 participant
Summary
Brings the conversation pull request docs from #808 up to date with the finished feature in LibreChat-AI/LibreChat#16982 and #16985 to #16990. The pages now cover GitLab merge requests (with nested group paths), Bitbucket Cloud, GitHub Enterprise Server and
*.ghe.comhosts, the token fallback variables for each provider, and whyprovider,hostandoauthare read fromlibrechat.yamlonly. They also cover per-user accounts throughoauth, with app registration steps for GitHub, GitLab and Bitbucket, the RedissharedCachefor replicas, a tuning reference, and new troubleshooting rows.#16876 has merged, so its "Pending" and "Older versions" notes are gone. Bitbucket,
sharedCacheandoauth(#16987 to #16990) are still open upstream and are marked Pending in the same style. A hidden comment says to remove those markers once the PRs merge.Change Type
Testing
pullRequestsYAML examples parse withagentsEndpointSchemaandconfigSchemafrom the LibreChat stack head.pnpm lint:prettier,pnpm typecheckandpnpm lintpass.pnpm buildpasses.Checklist
.envreference and Code Interpreter cross-link were updated