Repository navigation
Conversation
|
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: fb1461cd85
ℹ️ 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".
| light="/images/pull-requests/mob-menu-light.png" | ||
| dark="/images/pull-requests/mob-menu-dark.png" |
There was a problem hiding this comment.
Both mob-menu-light.png and mob-menu-dark.png show the menu and its PR #1234 entry at extremely low opacity, making the entry nearly indistinguishable from the background in either theme. Since this image is meant to show users where the small-screen pull-request control is located, recapture it without the dimming/transition overlay so the target menu item is readable.
Useful? React with 👍 / 👎.
| - The pull request number, with lines added in green and lines removed in red. | ||
| - A link that opens the pull request on GitHub. | ||
| - The pull request title. | ||
| - A **State** badge: Open, Draft, Merged or Closed. |
There was a problem hiding this comment.
The newly added conflict screenshot directly below this section shows the card badge as State: Conflicts, but this list says the only possible state badges are Open, Draft, Merged, or Closed. This makes the guide contradict its own example for a normal merge-conflict scenario; include Conflicts and clarify that it is displayed instead of Open when the pull request cannot merge.
Useful? React with 👍 / 👎.
| ### The status icon and dot | ||
|
|
||
| **Older versions:** `token` is required when the feature is enabled, and must be a `${NAME}` reference such as `"${GITHUB_PULL_REQUEST_TOKEN}"`. There is no environment variable fallback. | ||
| The icon color tells you if the pull request can merge. The dot next to it shows the state of the checks. |
There was a problem hiding this comment.
When the chat agent has an avatar—as in every new header screenshot—the checks dot is overlaid on that avatar rather than placed next to the pull-request icon; the icon carries the dot only when no avatar is available. Saying the dot is next to the icon directs users to the wrong part of the chip in the common avatar case, so document this conditional placement.
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
Follow-up to #808, which already merged. The Conversation Pull Requests page was written from the implementation spec, so it read like a reference. This makes it a user guide.
allowAllRepositories. The pages now describe onlyenabled: true, a${NAME}token reference andallowedRepositories. These can come back in a later PR once #16876 merges.public/images/pull-requestsand use the existingThemeImagecomponent.Still open and left as TODO comments in the page: where an admin sets the repository for a workspace environment, the first release version, and the changelog entry.
Testing
pnpm typecheckandpnpm lintexit 0, and the page compiles with@mdx-js/mdx.public/images.pnpm build, and how the page and images look in a browser.