Repository navigation
Docs: the hot-reload question is posted as longbridge/gpui-mobile#34 - #73
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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: 7a2fbb1713
ℹ️ 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".
| loader for the pushed library (`GpuiLibraryLoader`, fork branch | ||
| `dev-hot-loader`). Next: ask upstream where they want it | ||
| ([issue draft](docs/upstream/hot-reload-discussion.md)). A desktop-hosted | ||
| ([longbridge/gpui-mobile#34](https://github.com/longbridge/gpui-mobile/issues/34)). A desktop-hosted |
There was a problem hiding this comment.
When contributors follow this ordered work list, the entry still says the next action is to ask upstream where the loader should live, even though the newly linked issue and updated discussion document say that question was already posted. This leaves the planning status stale and can prompt someone to repeat completed work; change the text to record that upstream was asked and identify the actual next step, such as waiting for a response.
Useful? React with 👍 / 👎.
1 participant
Marks the draft from #71 as posted (longbridge/gpui-mobile#34) in the draft itself, in
docs/upstream/README.md(row 20), in MOBILE_PATCHES and in CONTRIBUTING_IDEAS item 4. Docs only.🤖 Generated with Claude Code